As we are wrapping up and nearing completion of this first batch of improvements, we are publishing release candidates of the Python implementation of the spec.
If those sound like useful features for az CLI, I would like to enquire about the required steps and process to have this library included as a dependency to this repository.
I would be happy to submit a pull request in due course obviously. Please let me know if that is something you would consider.
More than a feature request, this issue is my formal way to introduce JMESPath Community.
For many months we at JMESPath Community worked on brainstorming ideas for new features and curated a reasonably scoped set of new features as our first milestone.
The goal is to pick the JMESPath language were it left off and steward improvements to the specification at a quicker pace with a clear governance.
Amongst the new features being proposed one can find:
As we are wrapping up and nearing completion of this first batch of improvements, we are publishing release candidates of the Python implementation of the spec.
If those sound like useful features for az CLI, I would like to enquire about the required steps and process to have this library included as a dependency to this repository.
I would be happy to submit a pull request in due course obviously. Please let me know if that is something you would consider.