Dot key + filter

[Etwenn]

Dot key + filter

[Rudraksh2003]

The problem arises because dots are typically used as delimiters in JSONPath expressions, so having a key with a dot in it can lead to unexpected behavior.

In this case, since your key is "item.thing," it is being interpreted as a nested structure. You've tried escaping the dot with quotes, but it seems that the filter function is causing complications.

One way to approach this is to use the bracket notation to access the property. Here's an example that might work for your case:

json

['item.thing'][?(@.key=="match")].value
This way, you are treating "item.thing" as a single key rather than a nested structure. The bracket notation can help in cases where the key contains special characters like dots.

Your expression might look like this:

json

['item.thing'][?(@.key=="match")].value.get(0)=='b'

This assumes that the JSONPath library you are using supports the bracket notation for keys.

If this doesn't work, you might need to refer to the documentation or specific implementation details of the JSONPath library you are using to see if there are any special considerations or syntax for handling keys with dots. If the library supports escaping characters in keys, check for the correct syntax according to its documentation.