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.

Sign up for GitHub

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

Jump to bottom

Use raw map key when it cannot be keywordized #18

Closed
wants to merge 1 commit into from
Closed

Use raw map key when it cannot be keywordized #18

wants to merge 1 commit into from

Commits on Dec 15, 2013

  1. Use raw map key when it cannot be keywordized 

    YAML allows the keys in a map to be arbitrary nodes: scalar, sequence
or mapping. [1]  Prior to this commit, the *keywordize* option was
incorrectly setting map keys to `nil` for any keys that could not be
keywordized via `(keyword k)`.  For example, a valid integer key
"123: 456" would be parsed as {nil 456}, because `(keyword 123)`
evals to nil.

This commit fixes the issue by keywordizing any map key that can be
keyworded, and otherwise using the raw key if `(keyword k)` is nil.

[1] http://www.yaml.org/spec/1.2/spec.html#id2764044
    @elliot42
    elliot42 committed Dec 15, 2013
    Configuration menu
    Copy the full SHA
    be6efd3 View commit details
    Browse the repository at this point in the history