🐛 Fix for json path expecting an array #41
Merged
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
I believe simple assertions worked because the top level object was being cast into an array, but if any specific path returned an object you'd get a type error.
martin-helmich
approved these changes
Dec 22, 2020
|
👍 Good catch! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The recent update to
softcreatr/jsonpathintroduced a type error if the asserted path returned a hash, asgetData()declaresarrayas the return type.I believe simple assertions worked because the top level object was being cast into an array, and traversing as an array worked, but if any specific path returned an object you'd get a type error due to the new return type declaration.