-
-
Notifications
You must be signed in to change notification settings - Fork 746
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
YAML error when having dates as keys (upgrading to v4) #1930
Comments
You're using a date as a key? Didn't realize YAML would parse that into a date. Try wrapping it in quotes? |
Yes, I don't know it is the best idea I've ever had, but I do. Of course, if I enclose it into quotes, but then it is not a date anymore, but a string. |
Oh, you want it to act as a date? |
Yes I do. In v3, that used to work. I am just trying to find out if there is a way to make it work again or if I have to modify all my YAML files. |
I think you'll have to modify the YAML files. There's code to do stuff like Simplest thing is probably to stringify the key, then add an actual Data type row in it's sub-content. |
Is this still an issue? |
This is an issue for me too. I just tried updating an app to v4.2.1 and have experienced the same issue with integer keys, reported here #2238. Keys in YAML can be any type, they aren't bound to be strings. Integer keys definitely worked in v3 and that behavior has appeared to change in v4. |
I’ll add this to the test suite |
Fixed here: 1dc1611 |
I ran the build against |
Great, waiting for an upstream release of Bundler to put out the point release officially. |
This is may not be a bug, but it is at least an undocumented breaking change introduced in v4.
In my
data
dir I have YAML files that contain dates as key, for example:With v3, everything were fine, but with v4, I got the following error:
How can I revert to the previous behavior? (Of course, I can wrap all my dates into quotes, but I would appreciate to avoid that.)
The text was updated successfully, but these errors were encountered: