Merged
Conversation
Owner
|
@kgirzadas thanks a lot for fixing this! |
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.
This PR addresses a side effect introduced by the fix in #52, which resolved issue #51 related to preserving the original order of fields when flattening mixed fieldsets and fields.
In the current implementation,
flatten()method is used without a depth parameter, which unintentionally flattens too deeply. This causes issues during augmentation, especially when dealing with complex nested fields configurations.What’s changed:
flatten()method to use a depth of1, ensuring only the immediate level is flattened.