"full_path" incorrect when using doubledot notation and filters outside of an array

[cpj-cog]

When using double dot notation and a filter (like "$..@[?@=='val_b']") the matches do not have the correct path unless they are in an array.

The following is an example of a match with an incorrect path

from jsonpath_ng.ext import parse

example = {
    "key_a": "'val_a", 
    "key_b":  "val_b"
}
matches = parse("$..@[?@=='val_b']").find(example)
assert len(matches) == 1  # This assert passes
print(matches[0].full_path)  # This prints "[1]" which is not the correct path

print(matches[0].full_path.update(example, "hello"))
# The above will print the following
# {
#    "key_a": "'val_a", 
#    "key_b":  "val_b",
#    1: "hello"
#}

The following is an example of a match with the correct path.

from jsonpath_ng.ext import parse

example = {
    "key_a": "'val_a", 
    "key_b":  ["val_a", "val_b"]
}
matches = parse("$..@[?@=='val_b']").find(example)
assert len(matches) == 1  # This assert passes
print(matches[0].full_path)  # This prints "key_b.[1]" which is correct

print(matches[0].full_path.update(example, "hello"))
# The above will print the following
# {
#    "key_a": "'val_a", 
#    "key_b":  ["val_a", "hello"],
#}

[JakePi3]

I have a similar use case. I was originally using filters but I was able to get this down to a simpler form:

from jsonpath_ng.ext import parse

example = {
  "p": {"type": "Foo", "val": "a"},
  "s": [{"type": "Foo", "val": "b"}]
}

matches = parse("$..[*].val").find(example)

for m in matches:
  print(m.full_path)

# Prints three paths:
# p.[0].val
# s.[0].val
# s.[0].[0].val

That was the only form I could find that would capture both entries (but one is captured twice).

$..*[?type='Foo'].val captures only the middle case from above and I wasn't able to formulate a query that would capture the two nodes as intended.