-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
Missing escaping for uppercase "No" #188
Comments
However, it seems like yaml 1.2 dropped this insane handling of boolean values and only accepts At the very least, it's an inconsistency, as it handles lowercase |
As for me, I think I will switch to using https://github.com/processone/fast_yaml for my project, as I need 1-to-1 compatibility with the ruby yaml library. And since fast_yaml uses the same underlying libyaml, it should provide max compatibility between the two. |
fast_yaml seems to handle this case correctly, but unfortunately I get the "wrong" quotes. Not great either for my usecase...
|
Hi @Zinggi Thanks for raising this.
The quoted version is valid in both versions. So let's aim for that. |
Issue description
Similar to #184, I've found another issue with escaping:
correct would be:
It's already correct for lowercase 'no':
Link to documentation
https://yaml.org/type/bool.html
The text was updated successfully, but these errors were encountered: