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

Restore support for legacy unquoted string literals #32

Merged
merged 1 commit into from
Jul 7, 2016

Commits on May 23, 2016

  1. Restore support for legacy unquoted string literals

    While we definitely want to transition away from unquoted string
    literals, it seems reasonable to do that over time, similarly to how it
    was handled in jmespath.py.
    
    The reason for doing so, is to allow for a simple upgrade path, where a
    new version of jmespath.rb can be installed, and the software using it
    can transition all its configuration to use the new format, and then the
    jmespath.rb version could be upgraded to not even support these
    expressions.
    
    The tests were copied verbatim from jmespath.py, and are not included in
    the compliance test suite, so comes with an explicit license, which the
    compliance test suite does not. JSON doesn't allow for comments, so I'm
    not sure how to handle the attribution clause of the jmespath.py license
    grddev committed May 23, 2016
    Configuration menu
    Copy the full SHA
    95ac4b0 View commit details
    Browse the repository at this point in the history