IBX-3320: Unified content versions edit buttons logic #2058
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
barw4
changed the title
|
Kudos, SonarCloud Quality Gate passed!
|
ViniTou
approved these changes
Aug 22, 2022
konradoboza
approved these changes
Aug 22, 2022
adamwojs
approved these changes
Aug 22, 2022
mikadamczyk
approved these changes
Aug 22, 2022
webhdx
approved these changes
Aug 23, 2022
micszo
approved these changes
Aug 23, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Not sure about the desired behavior (right now we are forbidding from editing someone else's draft in the Back Office during conflict modal, unlike API - is this correct or should we allow it?) but the logic should be unified when it comes to version editing.
Related PR: https://github.com/ezsystems/ezplatform-page-builder/pull/961
Checklist:
$ composer fix-cs)