Round-trip configuration between JSON, YAML, TOML and XML. Useful for moving between CI systems.
Pick a source format and a target format. The input is parsed into a plain structure and re-emitted, which is exactly what you need when porting a config between two tools that disagree about syntax.
The parsers cover the subset of each format that appears in configuration files: scalars, nested maps, and sequences. Anchors, custom tags and mixed-content XML are out of scope.
Does this support YAML anchors and aliases? No. The parser handles the configuration subset — nested maps, sequences and scalars. Anchors, aliases and custom tags are not resolved.