Open chipsenkbeil opened 3 years ago
@chipsenkbeil do you plan to implement this request or you are hoping that contributors will pick this up?
@pratikpparikh, eventually, but for the moment I have other items higher up on my priority list. You or anyone else is welcome to tackle it first, if you'd like.
@chipsenkbeil @pratikpparikh We want to propose this feature to JMESPath and will include this in the next iteration for JMESPath Community.
@chipsenkbeil please note that a Rust implementation of JMESPath Community is pretty-much finalized.
Being discussed to formally be added to the spec here: https://github.com/jmespath/jmespath.py/issues/110
If I can get this library back up to working order including the macros, the next thing I'd like to see is an optional feature to add a non-standard recursive descent operator while the spec above gets discussed. Gated behind a feature like "nonstandard-recursive-descent", it would enable parsing
..
in the same manner as JSONPath and E4X, which expands the flexibility of jmespath.Once a standard solution became defined the spec, this feature could be sunset or default to the official solution.