Rudder

So, it seems that it won't go into 4.1 but 4.2. The idea and use case it still really clear.

Now that #12572 is added, we have the possibility to do that ticket in a simple way IF we accept to not modify the select/input layout, which is a big change.

I propose to add a new operator, JSON Path ("Name:JsonPath"), which would allows to use JsonPath in the right part of the ":". JsonPath is a kind of XPath for JSON: https://github.com/json-path/JsonPath.
The semantic would be "as long as the JsonPath selector returns a non-empty list, the search is ok and the node selected".

For example, let say you have a node with a property whose name is "user" and value is:

{
  "id": "xxxxxx",
  "accepted": true,
  "personal": {
    "name": "Smith Jones",
      "address": {
          "streetaddress": "7 24th Street",
          "city": "New York",
          "state": "NY",
          "postalcode": 10038
      },
      "phones": [
        {"type":"home","number":"(541) 754-3010"},
        {"type":"mobile","number":"(541) 754-9999"}
      ]
    }
  }
}

The following query would all select the node (I'm only displaying what would go in the input text field):

//select based on the value of a JSON leaf - boolean type
user:$.[?(@.accepted==true)]" }

//select based on the value of a JSON leaf - string type
user:$.personal.address[?(@.city=='New York')]

//select because "city" exists (whatever its value)
user:$.personal.address.city

//select based on a regex
user:$.personal.phones[?(@.number=~/.*123.*/)]

//select based on belonging to a set
user:$.personal.address[?(@.state in ['NY', 'CA', 'LA', 'TX'])]

It's just a glimpse of what is possible, JsonPath allows a lot of other operations. See examples in https://github.com/json-path/JsonPath.

This bug has been fixed in Rudder 4.3.2 which was released today.

• 4.3.2: Announce Changelog
• Download: https://www.rudder-project.org/site/get-rudder/downloads/