lib: add support for relative paths in decode definitions #10
Conversation
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
psurply
force-pushed
the
dev/relative_paths
branch
2 times, most recently
from
bc8217d to
3325de4
Compare
Some decode definitions use relative paths to reference fields. This changes refactors the CSV-based decoding flow to support these cases. This also removes the create_record_hierarchy() function from the public API. Signed-off-by: Surply, Pierre <[email protected]>
psurply
force-pushed
the
dev/relative_paths
branch
from
3325de4 to
40bb1f2
Compare
jlrivasp
approved these changes
Mar 13, 2025
Contributor
jlrivasp
left a comment
jlrivasp
left a comment
There was a problem hiding this comment.
Thank you so much for including this support
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.
Some decode definitions use relative paths to reference fields. This changes refactors the CSV-based decoding flow to support these cases.
This also removes the create_record_hierarchy() function from the public API.