Dot notation with wildcard after recursive descent

Setup

Selector: $..*

{
    "key": "value",
    "another key": {
        "complex": "string",
        "primitives": [0, 1]
    }
}

Results

Consensus

[
  "string",
  "value",
  0,
  1,
  [
    0,
    1
  ],
  {
    "complex": "string",
    "primitives": [
      0,
      1
    ]
  }
]

Other responses

Bash (JSONPath.sh)

[
  "string",
  "value",
  0,
  1
]

C (json-glib)

[]

Elixir (ExJsonPath)

Not supported

syntax error before: '*'

Elixir (jaxon)

[
  "value",
  {
    "complex": "string",
    "primitives": [
      0,
      1
    ]
  }
]

Perl (JSON-Path)

[]

Python (jsonpath-ng)

[
  "string",
  "value",
  [
    0,
    1
  ],
  {
    "complex": "string",
    "primitives": [
      0,
      1
    ]
  }
]

Python (jsonpath-rw)

[
  "string",
  "value",
  [
    0,
    1
  ],
  {
    "complex": "string",
    "primitives": [
      0,
      1
    ]
  }
]

Raku (JSON-Path)

[
  "string",
  0,
  1,
  [
    0,
    1
  ]
]

Ruby (jsonpath)

[
  "string",
  "value",
  0,
  1,
  [
    0,
    1
  ],
  {
    "another key": {
      "complex": "string",
      "primitives": [
        0,
        1
      ]
    },
    "key": "value"
  },
  {
    "complex": "string",
    "primitives": [
      0,
      1
    ]
  }
]

Rust (jsonpath)

Not supported

parsing error

Scala (jsonpath)

[
  "string",
  "value",
  0,
  1,
  [
    0,
    1
  ],
  {
    "another key": {
      "complex": "string",
      "primitives": [
        0,
        1
      ]
    },
    "key": "value"
  },
  {
    "complex": "string",
    "primitives": [
      0,
      1
    ]
  }
]

dotNET (Json.NET)

[
  "string",
  "value",
  0,
  1,
  [
    0,
    1
  ],
  {
    "another key": {
      "complex": "string",
      "primitives": [
        0,
        1
      ]
    },
    "key": "value"
  },
  {
    "complex": "string",
    "primitives": [
      0,
      1
    ]
  }
]

Errors

Golang (github.com-oliveagle-jsonpath) ¹

expression don't support in filter

Footnotes

• ¹ This implementation returns a single value where only one match is possible (instead of an array of a single value).
• ² This implementation returns a specific not found value if no match exists.
• ³ This implementation returns a specific not found value if a query that would regularly return a single match results in no match.