Add tests for invalid and uncommon filter literal values

[Marcono1234]

Generally for number literals since JSONPath uses the same syntax as JSON, test values from regular JSON libraries or JSON test suites could be used, for example https://github.com/nst/JSONTestSuite.

So if you have anything else in mind which should be covered, please let me know or feel free to add it yourself.

[gregsdennis]

Looks good. I think it needs a few more cases.

Thanks for the work.

[gregsdennis]

Just some remarks.

[f3ath]

Very nice. Revealed a few issues in my implementation.

[He-Pin]

Why treat +1 as an invalidate , I think we can just create it as valid.

[Marcono1234]

Why treat +1 as an invalidate , I think we can just create it as valid.

Similar to #90 (comment), because that is how it is defined in the JSONPath standard: A leading + is not allowed for number literals in filter selectors, see https://www.rfc-editor.org/rfc/rfc9535#section-2.3.5.1-10.

(This is also consistent with how JSON numbers are defined in the JSON specification.)