jmespath / jmespath/jmespath.jep

JEP Syntax Policy

Open
#9 2 comments 2 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
10
Forks
3
PR merge metrics
No merged PRs in 30d

Description

One of the qualities I enjoy of JMESPath is its syntactic simplicity.
I have seen a number of proposals to introduce new syntax for various purposes that has me concerned.
One example is adding a regex operator.
I would like to propose that operators and syntax be reserved for transforming, referencing, and subscripting data structures and not data values. All value specific operations should be implemented as functions. The exception to this would be arithmetic operators intended to operate on values.
This means all string operations other than those that could be reasonably described by an arithmetic operator should be implemented as a function.

Having complex value operations described as functions makes JMESPaths more readable.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.