Replies: 1 comment
-
|
Since one of Rye's focuses is the devops / backend Yaml and Toml will surelly need to be added. I just didn't need them so far. Yaml is whitespace sensitive format, so regular Rye parser wouldn't work as it would just ignore the indentation. There is a whitespace sensitive parser for some idea, co-language called Spruce, but probably there would be edge cases for proper Yaml anyway so it's the best to use a yaml parsing Go library and integrate it. The problem upfront is that I looked at a library now and it seems it maps yaml to static struct at least by default, but there usually is a more dynamic way, either callback driven or something like Dom, to use it in Rye then. If you need it urgently you can create an issue and I will try to implement it when I find time (and find a good path to it). If not I would rather first implement CLI parsing that is already an issue first (of such open things ... besides regular workd on more core of the language (improved terminal use, eror reporting, parser ...) |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Are there any plans in the near future to support handling the yaml (data serialization) format ? Or do you think that the current builtin functions, value types,... can handle yaml files ?
Beta Was this translation helpful? Give feedback.
All reactions