Repository navigation
Conversation
This was referenced Oct 7, 2026
This branch has not been deployed
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 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.
Fixes #15602
Imported fieldset sections are only preserved when the import sits directly in a blueprint (
Tab::toPublishArray()). Anywhere else, inside Replicator/Bard sets, Grid/Group fields, or another fieldset, they're always flattened. The CP still offered the "Section Behavior" control in those places, so choosing "Preserve" looked like it should work but did nothing.This PR:
section_behaviorin those contexts.The contexts are detected with the existing
isInsideSetandisInsideConfigFieldsinjections, plus a newisInsideFieldsetprovided by the fieldset editor. The check lives in onePreservesImportedSectionsmixin.This only changes the UI. Supporting collapsible sections inside sets would be a separate feature.