Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for using an ordered dictionary #94

Merged
merged 1 commit into from
Sep 23, 2015

Conversation

jamesls
Copy link
Member

@jamesls jamesls commented Sep 19, 2015

This isn't part of the JMESPath spec (we use the JSON
types and a JSON object has no key order). In order to
still accomodate this use case, I've added an Options class
that can alter how an expression is interpreted. You can provide
a specific dict cls that should be used whenever the interpreter
creates a dict as the result of evaluating an expression.

This gives people that want this option a way to do it without
having to comply with the JMESPath spec.

Fixes #89

This isn't part of the JMESPath spec (we use the JSON
types and a JSON object has no key order).  In order to
still accomodate this use case, I've added an Options class
that can alter how an expression is interpreted.  You can provide
a specific dict cls that should be used whenever the interpreter
creates a dict as the result of evaluating an expression.

This gives people that want this option a way to do it without
having to comply with the JMESPath spec.

Fixes jmespath#89
@jamesls jamesls merged commit 6be33c4 into jmespath:develop Sep 23, 2015
@ErwanPigneul ErwanPigneul mentioned this pull request Sep 23, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant