Cannot read properties of undefined (reading 'match') on an absent field

[Scratch-net]

Describe the bug

This error gets thrown if match field does not exist

Code sample or steps to reproduce

{
    "items":[
        {
            "name": "John Doe",
            "country": "USA"
        },
        {
          "country": "USA",
          "age":25
        }
    ]
}

//fails
$.items[?(@.name.match(/.*oe/))]

//only way to make it work
$.items[?(@.name && @.name.match(/.*oe/))]

Console error or logs

Error: jsonPath: Cannot read properties of undefined (reading 'match'): @.name.match(/.*abc/)

at JSONPath.Object.<anonymous>.JSONPath._eval
at JSONPath.Object.<anonymous>.JSONPath._walk
at JSONPath.Object.<anonymous>.JSONPath._trace
at JSONPath.Object.<anonymous>.JSONPath._trace
at JSONPath.Object.<anonymous>.JSONPath.evaluate

Expected behavior

no error gets thrown, no results returned

Environment (IMPORTANT)

• JSONPath-Plus version:v7.2.0

Desktop**

• NodeJS and browser

[brettz9]

In the json-path-comparison project, this does look like it should work per this example (which does indeed err in jsonpath-plus): https://cburgmer.github.io/json-path-comparison/results/filter_expression_with_subpaths_deeply_nested.html

PRs welcome.

[80avin]

There's an option ignoreEvalErrors in version 9.0.0.

It was lacking documentation, to fix which I've created #219

[brettz9]

I think we need a change to default that to true given the cross-implementation behavior.

[Scratch-net]

Ignoring errors won't solve the problem though, wouldn't it?

[brettz9]

It should in fact fix it. The errors we are ignoring are those that err because they don't find any parent object. If we ignore those errors, jsonpath-plus can continue to find legitimate values (where the parent object does exist).

[Scratch-net]

Oh, that would be nice to try but there's no such property in jsonpath.d.ts

[brettz9]

As per #218 (comment) , it was lacking docs. Just suppress the TS error for now; it's there.

[Scratch-net]

Yep, works. Thanks!