[4.x] Prevent ensuring fields on entries if they already exist #8926
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
duncanmcclean
changed the title
jasonvarga
deleted the
fix/unable_to_unlocalize_slug_in_the_blueprint_builder
branch
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.
This pull request prevents fields from being ensured on entry blueprints if they already exist. Without this check, any changes you made to the config of any of the ensured fields would be overwritten the next time you save the blueprint.
I've added the check for this in
Collectionwhere we're ensuring them but happy to do something "upstream" (eg. in theBlueprintmethods) if you'd rather go down that route.Fixes #2743.