A Sub-Attribute after a Value Path causes an 'unexpected token' error

[mastermatt]

emails[type eq "work" and value eq "[email protected]"]
emails[type eq "work"] and emails.value eq "[email protected]"
emails[type eq "work"].value eq "[email protected]"

The three above filters are all functionally identical, however, the last one throws:
Error: unexpected token .value eq "[email protected]"

I'll note that the syntax throwing the error is not explicitly listed in the examples of section 3.4.2.2 and the wording of that section leaves this syntax up in the air. However, section 3.5.2 (Modifying with PATCH) does include this syntax in its examples and callouts section 3.4.2.2 as the definition.
More importantly for my personal use case, Azure AD seems to use this syntax to query users (docs).

... a GET to /Users with a filter must allow for both userName eq "[email protected]" and emails[type eq "work"].value eq "[email protected]" queries.

---

I started working on a PR for this, but decided I should open an issue first and confirm what the expected result should be.
I presumed the desired output would an implicit and operation at the top level. e.g.

{
  "op": "and",
  "filters": [
    {
      "op": "[]",
      "attrPath": "emails",
      "valFilter": {
        "op": "eq",
        "attrPath": "type",
        "compValue": "work"
      }
    },
    {
      "op": "eq",
      "attrPath": "emails.value",
      "compValue": "[email protected]"
    }
  ]
}

[thomaspoignant]

Hello @mastermatt I was reading your issue and I think you are right, something is missing here.
If you can work on the PR it would be awesome 🙏.