JsonPath.Net

1.0.1.x

#711 - Nuget package meta-data updates; no functional changes from previous version.

1.0.1

Fixed an issue around operator precedence in boolean expressions.

1.0.0

JSON Path RFC 9535 has been released! (No functional changes from 0.8.0.)

0.8.1

#653 - @Emcrank applied modifications to support .Net Standard 2.0.

0.8.0

Updated for multi-framework support with .Net Standard 2.0 and .Net 8 with Native AOT support, including updating System.Text.Json from v6 to v8.

Breaking changes

Dropping support for .Net Standard 3.1 - May still be used, but exact behavior cannot be guaranteed.
JsonNodeExtensions.TryGetSingleValue(this JsonNode?) and .TryGetSingleValue(this NodeList?) updated to the bool Try...(out ...) pattern.

Additions

JsonPath.TypeInfoResolver to expose all of the type resolvers contained in the library. Can be used to create a combined SerializationOptions by using a Json.More.TypeResolverOptionsManager in your JsonSerializerContext.

0.7.0

#583 - Updated NodeList to implement IEnumerable<T> instead of IReadOnlyList<T>, which enables follow-on Linq queries, making the entire JSON Path evaluation a deferred execution query. Thanks to @qt-kaneko for explaining a use case that led to this change.

Technically this is a breaking change. The .Count property and indexer defined by IReadOnlyList<T> were left implemented on NodeList, so this shouldn’t impact consuming code, but there is a possibility.

It’s also important to note that .Count is now backed by Linq’s .Count() method, and the indexer is backed by Linq’s .ElementAt() method, so calling these isn’t zero-cost, like they once were. They will now invoke an evaluation of the path.

0.6.7

Whitespace between multiple selectors inside brackets was supported for .Parse() but not .TryParse(). Thanks to @Andrej-Peplinski for reporting this.

0.6.6

Adds support for + in number literals, e.g. +24 and 1e+5.

0.6.5

Update .AsJsonPointer() to allow $[1,"1"] pattern discussed in https://blog.json-everything.net/posts/paths-and-pointers-correction/.

0.6.4

#495 - .TryParse() with empty string throws exception. Thanks to @ben-wckdrzr for reporting this.

0.6.3

Test Suite #41 - ANBF allows for whitespace between segments.

0.6.2

#465 - Exposes more of the JSON Path object model, while making the exposed API more consistent.

0.6.1

#463 - Fixed implementation for string comparisons in filter expressions. Thanks to @idefy for reporting this.

0.6.0

Updated support for whitespace in all the right places.

Changed PathParsingOptions.TolerateSurroundingWhitespace to TolerateExtraWhitespace which now enables support for whitespace pretty much everywhere.

0.5.2

Improved support for regular expressions matching unicode text.

0.5.1

Added optional support for:

allowing leading and trailing whitespace
in operator in expressions
JSON constructs as literals in expressions
relative paths (starting a path with @)

0.5.0

Updated to meet the requirements in draft 11.

Update function definition
- only name is required by the interface
- functions must now inherit from ValueFunctionDefinition, LogicalFunctionDefinition, or NodeListFunctionDefinition
- Evaluate() is now detected via reflection at registration time
  - return type must conform to the base class
  - any count of parameters are supported, but they must be of type JsonNode, bool, or NodeList
  - only one evaluation method per function class
Added value() function
Moved parsing of math operators behind PathParsingOptions.AllowMathOperations, which defaults to false
FunctionType now matches the type system in the spec
ParameterType removed and usages replaced with FunctionType
NodeList implicit casts removed as they are no longer defined by the spec
Fixed a parsing issue that allowed non-singular paths in filter expressions

0.4.0

Updated function definition
- list parameter sets to support type checking and overloads rather than a minimum and maximum parameter count
- add return type to support type checking within expressions
fixes around TryParse() to ensure that it doesn’t throw exceptions (at least not from this code)
more fixes based on expanded tests in the compliance test suite

0.3.3

I added a bunch of tests to the JSON Path test suite and found a few bugs in filter expressions. This release fixes those bugs.

Some copy/paste/forgot-to-edit issues with </<=/>/>=
Not extracting string values correctly in comparisons
Not treating null values correctly when evaluating local paths (e.g. @.a)

0.3.2

#364 - count(), match(), and search() functions are not registered and so cannot be parsed. Thanks to @amis92 for finding and reporting this.

0.3.1

Fixed an issue in search and match function evaluation.

0.3.0

#281 - Complete rewrite to support JsonNode and align with specification. #351 - Fixes issues parsing $.['foo'] (basically removes support since the .[] syntax is invalid).

Changes of note:

Expression functions are supported and custom functions can be created.
.length has been replaced by length() function.
Available functions:
- length() - Length of values (objects, arrays, & strings)
- count() - Length of nodelists
- match() - Precise regex matching (uses implicit anchoring)
- search() - General regex matching (does not use implicit anchoring, more like JSON Schema’s pattern keyword)
Expression engine is more robust.
No context object needed for evaluation.
Removed experimental feature of $ref resolution since it’s not in the spec. (See the JSON Referencing proposals from the JSON Schema group at https://github.com/json-schema-org/referencing)

0.2.1

#243 - Updated System.Text.Json to version 6.

Fixed issue with parsing recursive descents into quoted-index property names, e.g. $..['foo']. Previous versions added two recursive descent selectors, which resulted in duplicate entries in the results.