Christoph Burgmer

See commit 89d538d0f176a00c3a08529c664b2646ffe343a0 Make sure to look at the master branch (default is "trunk").

I like to thing of there being at least two different problems many people try solving in this space: That of selecting values, and that of transforming the original JSON...

> @cburgmer what's the support for something like `$["a","b"]`? I'm not sure I've seen that anywhere. I'm talking about the union operator with two keys: https://cburgmer.github.io/json-path-comparison/results/union_with_keys.html. You will get the...

For further reference, Ruby's jsonpath has a "parens notation" (https://cburgmer.github.io/json-path-comparison/results/parens_notation.html) to select a subset: `$(key,more)`. Other implementations might have found their own syntax for supporting something like that, this is...

Fixed and released under 0.0.19.

More than happy to merge PRs :) I myself am currently not using this library, so have little need for changes.

I haven't used Vite, and haven't kept track of the last few years of the JS ecosystem. Back then when this library was created Grunt used to be the thing....

This should not be considered a bug in the implementation. It might be possible with additional handling (read: implementing code to do that) to avoid those warnings, with no improvement...

Looks good! Manually merged in 66589d6a9a0ccc799e1f5a0 It should be clear that the consensus does not respect RFC9535, it only reflects the status quo of (often antiquated) implementations. Hopefully there is...

Ah, if the consensus field is missing (e.g. https://github.com/cburgmer/json-path-comparison/blob/master/regression_suite/regression_suite.yaml#L50), then no consensus was reached and only a certain tendency might be derived (https://cburgmer.github.io/json-path-comparison/#array_slice_with_large_number_for_end_and_negative_step). I believe doing nothing is the only...