James Saryerwinnie

Just want to clarify a few things here to prevent confusion. There is one official version of the JMESPath specification, which is the version maintained in this repo here. Other...

I had an updated grammar somewhere that had part of the precedence baked into the grammar. It wasn't complete but it had the or/pipe's worked out. I'll see if I...

I'm starting to pick up work again on JEP-9 (the improved filters with ands, nots, parens, etc) and I want to incorporate this grammar as part of that work. I'm...

Hey everyone, sorry for not being present in this project for a while, but I'm still alive and I'll have more time to allocate working on this project now. Other...

I created the repo a while back but I need to port the existing proposals over to the site, was converting the existing proposals over to markdown just to make...

Closing out old issue. > with the move to the jmespath.jep repository, does that invalidate the already well written PRs pending in the jmespath.site repository? No, I'm moving issues related...

Closing out old issue, this has been fixed.

Ok I've linked: - [compliance tests](https://github.com/jmespath/jmespath.test/commit/2b97867f163559e3560d081155320edd45b31f0d) - [python implementation](https://github.com/jamesls/jmespath/commit/3d53ece91ca188288ee9ae560fb1ba52d4ecd7d0) So far everything seems reasonable. Semantics make sense to me. We're borrowing from existing languages where this feature has been around...

cc @kyleknap @danielgtaylor, if you want to comment, though don't feel obligated.

FWIW, I also have an initial implementation of the javascript version as well (https://github.com/jmespath/jmespath.js/commit/25c22b2192988d11e5fe40795c28281880e4f50e), and I would say the implementation is almost borderline trivial, which is what I like (and...