-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support recursive dicts #3
Conversation
This is really fancy! Should it be made even more general, for example jsonpath lookups or something? (I'm not even sure what the right term would be, clearly it's not literal json) I'm definitely happy for this, just wonder if it should be made even better. Or maybe that's too much change. |
I've updated the GitHub action if you want to merge/rebase. |
I was originally thinking of something like json path lookups - I think that could be useful in the future - for now this is a good stopgap for our use case. |
77064db
to
a2ba3d5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like the idea but some comments, especially about the substring matching.
- This overlapped with doc1_original causing problems.
Duplicate name of the test fixture |
And I updated the release action and released! Thanks again! (I commented out the partial_match part in the documentation since it wasn't implemented, but having it be a configurable option is completely reasonable by me if it helps your use cases). |
This is great! Thanks for getting it past the finish line! |
No description provided.