fix: clone field within a group field type returns null values#185
Merged
fix: clone field within a group field type returns null values#185
Conversation
…y' to better compensate for clone fields, specifically when groups are cloned
This was referenced Mar 4, 2024
Pull Request Test Coverage Report for Build 8a34ff48313691d4393305f21bf89808a50005f3-PR-185Details
💛 - Coveralls |
Merged
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
2 participants
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.
What does this implement/fix? Explain your changes.
checks if the value is being passed down with the' __key' or the 'key' to better compensate for clone fields, specifically when groups are cloned
Does this close any currently open issues?
fixes #184
fixes #151
Any other comments?
I believe this addresses the issues reported in #184 and #184
Below are some before/after examples:
Issue 184
Following the reported steps to reproduce (see #184):
Before
After
Issue 151
Following the reported steps to reproduce (see #151):
Before
After