Using != in jsonpath boolean expression leads to syntax error.

[msterin]

What is the current bug behavior?

Using != in jsonpath boolean expression leads to syntax error.

Steps to reproduce

Run hurl with the following file:

POST https://httpbin.org/anything
[
    {
        "projectName": "p1",
        "projectId": 11
    },
    {
        "projectName": "p2",
        "projectId": 21
    }
]
HTTP 200
[Asserts]
#
# expected to pass, passes
jsonpath "$.json[?(@.projectName == 'p2')].projectId" nth 0 == 21
#
# ====> expected to pass, fails with the "JSONPath expression '$.json[?(@.projectName != 'p1')].projectId' is not valid"
#  
jsonpath "$.json[?(@.projectName != 'p1')].projectId" nth 0 == 21

What is the expected correct behavior?

a != b is sexpected to work and generate 'true' when the a != b

Execution context

$ hurl -V
hurl 5.0.1 (x86_64-apple-darwin23.0) libcurl/8.7.1 (SecureTransport) LibreSSL/3.3.6 zlib/1.2.12 nghttp2/1.61.0
Features (libcurl): alt-svc AsynchDNS HSTS HTTP2 IPv6 Largefile libz NTLM SPNEGO SSL UnixSockets
Features (built-in): brotli

Possible fixes

n/a

[fabricereix]

Hi @msterin,
The support for JsonPath filter in general is quite limited for the time-being.
There is now a spec that we will try to implement.

[msterin]

@fabricereix - thanks for the reply. Understood and looking forward for the spec implementation.
Hurl with jsonpath is a great flexible tool , happy to see it's getting better.