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

Jump to bottom

Unexpected behavior when using unquoted date as key #48

Closed
paranoiq opened this issue Feb 28, 2020 · 1 comment
Closed

Unexpected behavior when using unquoted date as key #48

paranoiq opened this issue Feb 28, 2020 · 1 comment

Comments

@paranoiq
Copy link

@paranoiq paranoiq commented Feb 28, 2020 •
edited

Version: 3.1.1

it is ok to use keys like 2020-02 without quotes, but 2020-02-02 is a syntax error.

foo:
    2020-02: bar # ok
    2020-02-02: baz # fails

i would expect the behavior to be the same regardless of number of dashes, but maybe the first case working is this some side effect of parsing numbers in sci notation?

anyway, it would be really nice if this works : ]
@dg dg closed this as completed in 8d184cf Feb 28, 2020
@paranoiq
Copy link
Author

@paranoiq paranoiq commented Feb 29, 2020

wow! dík! : ]

dg added a commit that referenced this issue Mar 4, 2020
@dg
Decoder: date-time is not decoded in keys [Closes #48]
85bdf2e
dg added a commit that referenced this issue Mar 4, 2020
@dg
Decoder: date-time is not decoded in keys [Closes #48]
7aaad9f
dg added a commit that referenced this issue Mar 4, 2020
@dg
Decoder: date-time is not decoded in keys [Closes #48]
6a83f3e
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@paranoiq