Uh oh!
There was an error while loading. Please reload this page.
[4.x] Fix "A field with a handle of X already exists" error when editing fieldsets - #9718
Merged
jasonvarga merged 1 commit intoMar 12, 2024
Merged
Conversation
jasonvarga
deleted the
fix/fieldset-field-with-handle-already-exists-error
branch
March 12, 2024 19:27
This file contains hidden or 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
Sign up for freeto 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 fixes an issue when editing fieldsets where you'd run into this error message when applying changes to a field: "A field with the handle of ... already exists".
This validation message should only be displayed when there's already a field in the blueprint/fieldset with the same handle as the field you're applying.
For some reason, the code inside the
->when()closure sometimes wasn't being called, meaning it wouldn't ignore the current field when looking at all fields for those with the same handle.Fixes#9716.
Caused by #9337.