JMESPath Community 1.1

[springcomp]

JMESPath Community 1.1.0 implements most of those ideas.

After working for many months on various ideas we think that we have come up with a reasonable set of useful improvements to the JMESPath Community specification.

Here are the proposals that included in the specification.

• JMESPath Community General Behaviour
  • JEP-019 Standardizing pipe expression evaluation. ✔
  • JEP-015 Enabling string slices. ✔
• New Syntax
  • JEP-016 arithmetic-expression.✔
  • JEP-017 Root Node Reference with the $ token. ✔
  • JEP-020 Compact syntax for multi-select-hash.
• New Functions
  • JEP-011 Lexical Scoping and the let() function. ✔
  • JEP-013 Object Manipulation items(), from_items() and zip() functions. ✔
  • JEP-014 String functions. ✔
  • JEP-018 Grouping group_by() function. ✔

All those features are demonstrated here.

History

Date	Description
2022-10-13	Lexical Scoping proposal has been assigned number JEP-011
2022-10-13	Object Manipulation Functions proposal has been assigned number JEP-013
2022-10-13	String Functions proposal has been assigned number JEP-014
2022-10-14	String Slices proposal has been assigned number JEP-015
2022-10-14	Arithmetic Expressions proposal has been assigned number JEP-016
2022-10-14	Root Node Reference proposal has been assigned number JEP-017
2022-10-20	Grouping Function proposal has been assigned number JEP-018
2022-10-29	Added proposal to standardize pipe expression evaluation
2022-11-03	Compact Syntax for multi-select-hash proposal has been assigned number JEP-020
2023-02-28	Edited post to document the exact scope of Milestone-1.1

[springcomp]

I still feel like we would need to introduce a reduce operation, but we need wider community feedback. In particular, we need to contrast my preferred suggestion with the need to include a new token – e.g $ – to refer to the accumulated value within a reduce operation, or even in a wider context. Incidentally, it seems my proposal was almost being considered early on in the design of JMESPath.

I also think standardizing undocumented behaviour and enabling empty multi-select-hash should be included in this milestone.

What do you think?

[springcomp]

Using $ as a reference to the root node is a specific case of using the let() function.

Some members feel that it conflicts with the Lexical Scoping proposal.
Others think it simplifies a common case.

Please, vote.
Should we include both?

[hell-racer]

I think Root Node Reference should be in New Syntax section, and not in New Functions section.

[springcomp]

Thanks for the feedback. Indeed you are right.

[kit494way]

It would be good to know in which language each specification is implemented.

[springcomp]

It would be good to know in which language each specification is implemented.

I think the libraries page is trying to convey just that.
Please, let me know how I can improve it and make it clearer.