Closed 20010930 closed 1 year ago
I would call the change a bug fix. It's noted in the release notes in the CHANGELOG.md file. The reason for that is that the https://datatracker.ietf.org/doc/draft-ietf-jsonpath-base draft use Nothing
to indicate a field is missing which makes sense as null
is a valid value. So @.qualifier == null
should return true if the qualifier has a value of null
.
I'm not sure what the data looks like but does that describe your situation?
Indeed it describe it ;).
So, all good? Can this be closed?
Hello,
I think there is a regression in the version [1.18.0]. Issue in
When i try to update the field using the Set method in set.go ;).
More precisely the param @.qualifier == null seems to be the issue. In my case I can use this synthax in the latest version of the library !@.qualifier to make it work.