You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For objects, it's currently very difficult (if not impossible) to have access to the key and the value in the same scope of the expression. This function would decompose objects into Array<[key:value]> such that every key corresponds to a decomposed value.
In javascript (typescript) this might look something like:
Could this be done with the proposed let() function? I like this proposal but it could potentially violate the "one way of doing things" policy that has kept JMESPath simple.
This and an entire class of other proposed functions would definitely be supported by the let function. JEP 11: The let() Function is a great proposal as it generalises this core issue proposed here. Given it was proposed in 2015 I really hope there will be some progress on it.
For objects, it's currently very difficult (if not impossible) to have access to the key and the value in the same scope of the expression. This function would decompose objects into Array<[key:value]> such that every key corresponds to a decomposed value.
In javascript (typescript) this might look something like:
Which produces the following:
These could then be piped to expressions that filter on keys or project keys into new objects/arrays
The text was updated successfully, but these errors were encountered: