EZP-31039: Skip requirement of sort params when updating Location via REST #57
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
adamwojs
approved these changes
Oct 26, 2020
lserwatka
approved these changes
Oct 26, 2020
tomaszszopinski
approved these changes
Oct 27, 2020
|
Merged into master: 276f371 |
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
updateLocationAPI method doesn't require the existence of sort params inLocationUpdateStruct(it will use params already stored in the Location itself), we can remove them when parsing REST data.Related
ezplatform-admin-uiPR: ezsystems/ezplatform-admin-ui#1643Parent
ezpublish-kernelPR: ezsystems/ezpublish-kernel#3071TODO:
$ composer fix-cs).