Add DeepDataIterator and data field path building#48
Merged
Conversation
As much as possible we want to avoid field path being built manually as this is more error-prone and makes it hard for the syntax to evolve.
gbenadikar
approved these changes
Oct 23, 2025
gbenadikar
approved these changes
Oct 23, 2025
To be used for exhaustive, recursive traversal of record data, for example for validation purposes.
vlaurin
force-pushed
the
deep-data-iterator
branch
from
17b1c37 to
9d2be42
Compare
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.
No description provided.