This repository has been archived by the owner on Apr 20, 2021. It is now read-only.
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.
As noticed in #260 there is an issue when trying to check if a JSON node is null or not.
I'll rather prefer to thow an exception here in order to avoid a "silent" return in a try/catch block.
The PropertyAccessor's getValue() method will throw an
throwInvalidArgumentException
exception in this case.Description:
Given I have the following JSON to test, for example (any valid JSON will do the trick):
And I want to check that "notExistingField" should not be null.
The following step is a success:
And the JSON node "notExistingField" should not be null
.I was doing TDD, and I expected my test to fail.
Before I add/update tests, let me know what do you think about it.
Thanks.