lyaml
lyaml copied to clipboard
gvvaughan
Any plans to support yaml 1.2?
Specifically I am concerned about 1.1's implicit typing leading to issues like the Norway problem, where NO is converted to boolean false.
https://hitchdev.com/strictyaml/why/implicit-typing-removed/
This kind of implicit typing was removed from YAML 1.2
I would LOVE to support YAML 1.2! But, I also do not want to write a full implementation. lyaml is a thin Lua wrapper for the existing libyaml, and unfortunately that library only supports YAML 1.1.
If you know of a good, reasonably fast, actively supported, well distributed YAML 1.2 library, I would be happy to schedule a version of lyaml that uses its API.
Depending on your interest and resources, I am sure you could make a lot of people... myself included... very happy if you forked libyaml to add 1.2 support, and then lyaml would get it for free!
Thanks for replying quickly.
Re library, maybe this meets your criteria?
https://github.com/mikefarah/yq/#install
Not used it yet, just on my radar as something i might use in bash scripts.
Afraid I am focusing my time on my own project, so I doubt I will have time to help further anytime soon. Sorry!
On Sat, 7 Jan 2023, 18:36 Gary V. Vaughan, @.***> wrote:
I would LOVE to support YAML 1.2! But, I also do not want to write a full implementation. lyaml is a thin Lua wrapper for the existing libyaml, and unfortunately that library only supports YAML 1.1.
If you know of a good, reasonably fast, actively supported, well distributed YAML 1.2 library, I would be happy to schedule a version of lyaml that uses its API.
Depending on your interest and resources, I am sure you could make a lot of people... myself included... very happy if you forked libyaml to add 1.2 support, and then lyaml would get it for free!
— Reply to this email directly, view it on GitHub https://github.com/gvvaughan/lyaml/issues/51#issuecomment-1374568385, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABF2CC3XLNSGBYGLMGI4ZD3WRGZSJANCNFSM6AAAAAATTUHU4U . You are receiving this because you authored the thread.Message ID: @.***>