Support indexing on arrays in body matching

[fbryden]

Indexing is currently not supported in the body matching path of config v2.

This adds support for it.

Allows two scenarios, where we attempt scenario 1, and fallback to scenario 2 in case we don't find a value at that path.

The query path is a.b.0.c. Both scenarios will match.

Scenario 1

{
  "a": {
    "b": [
      {
        "c": "value"
      }
    ]
  }
}

Scenario 2

{
  "a": {
    "b": {
      "0": {
        "c" : "value"
      }
    }
  }
}

• JIRA link

[aimenebelfodil]

More of a curisotiy? @fbryden why a.b.0.c and not a.b[0].c
https://www.rfc-editor.org/rfc/rfc9535#name-array-slice-selector 🙇

[fbryden]

@aimenebelfodil
sort of a fair suggestion, but it heavily simplifies the parsing of the path string.
Your suggestion requires slightly more complex parsing.

[fbryden]

@aimenebelfodil we currently split on . and treat each element as a way to traverse one layer deeper

[vinckama]

Would it be possible to treat arrays path differently than maps? For instance, would it be possible to follow the jsonpath syntax? It's the same syntax used in synthetics to validate the body response.

[fbryden]

@aimenebelfodil @vinckama I've implemented jsonpath-like accessing in 4393fa1

[aimenebelfodil]

🙇

[vinckama]

Perfect, I did not see the comment at that time. Thanks for pushing this 🙇

[aimenebelfodil]

LGTM thanks

• Could you add a test where root is an array?
• Another test where we do have nested array
• And update the PR description too 🙇 with the latest updates

Thanks @fbryden 🥇