Version 2.0.0
Breaking changes
These API changes should only affect you if you're customizing the JSONPath parser, defining custom JSONPath selectors or inspecting JSONPath.selectors
(now JSONPathQuery.segments
). Otherwise query parsing and evaluation remains unchanged. See issue 11 for more information.
- Renamed
JSONPath
toJSONPathQuery
to match terminology from RFC 9535. - Refactored
JSONPathQuery
to be composed ofJSONPathSegment
s, each of which is composed of one or more instances ofJSONPathSelector
. - Changed abstract method
JSONPathSelector.resolve
andJSONPathSelector.lazyResolve
to accept a single node argument instead of an array or iterator of nodes. Both still return zero or more nodes.