-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IBX-6211: Added product edit route to EDIT_VIEWS const #43
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall looks good, but can you double-check if CI fail is related?
@konradoboza The error is independent of the PR, but I push a fix |
c066d75
to
f639d99
Compare
Summoning @mnocon to look if the Behat-related changes are ok. ;) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 for Behat changes, thanks for taking care of it! 💪
f639d99
to
92a6096
Compare
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
'ibexa.content.translate', | ||
'ibexa.content.translate_with_location', | ||
'ibexa.user.update', | ||
'ibexa.product_catalog.product.edit', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ibexa/content-forms shouldn't refer to symbols defined in ibexa/product-catalog.
As this solution is not acceptable, I am closing this ticket and a new one will be opened in ibexa/product-catalog. I will also create a new PR for the changes to the Behat tests that this PR was supposed to make |
Jira: https://issues.ibexa.co/browse/IBX-6211
The problem was not saving the date, but the fact that input always had data-action-type set to create, this change will allow to recognize whether we are editing or creating content