[6.x] Fix nested revealer fields #12362
Open
+15
−1
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 attempts to fix an issue where Revealer fields weren't working in nested fieldtypes like Bard & Replicator.
This was happening because the
revealerValuesobject we're getting from theContainerand passing toShowFieldlooks like this:However, when the field condition validator attempts to get the field's value, it fails, because it's trying to find a value using the revealer's field handle, not its "full dotted path".
This PR fixes it by only passing the "relative" revealer values to
ShowFieldand flattening the keys to just the field handles.Fixes #12099.