Closed matthiasbeyer closed 3 months ago
It might be unmaintained, but as long as it's working and not causing any problems in config-rs
that should be fine to leave as-is? Alternatively instead of removing YAML support entirely, it only really requires changing the format/yaml.rs
file right?
There's an actively developed serde yaml crate, although it's unclear if it's at parity feature wise.
Ah yeah, I didn't see that. I would prefer switching to another YAML implementation rather than removing support completely.
Just a heads-up, not sure if you get notifications for new PRs but https://github.com/mehcode/config-rs/pull/474 has been open without any engagement nearing two weeks now.
If you merge #474 first, I'll rebase #472 to accomodate, otherwise #472 has a separate commit focused on the YAML support and switch, which should be fine as you prefer merge commits over squash commits, there is little advantage then from merging #474 . Both PRs cross-reference each other, so that information on #474 shouldn't be difficult to find (as those additional details aren't in the commit message).
Ah yeah, I didn't see that. I would prefer switching to another YAML implementation rather than removing support completely.
Apparently there's the yaml-rust2 drop-in replacement that is actively maintained. I've created #554 with this change to fix #553 which arose in the meantime.
Originally posted by @polarathene in https://github.com/mehcode/config-rs/issues/466#issuecomment-1751664819
I know that YAML is widely used as a configuration language in some ecosystems, so I am a bit undecided about this one. If someone wants to go ahead and remove YAML support, though, I would merge such a patchset.