> "To that end, configuration is defined in a YAML file called the request collection"
Genuine question, why do people use YAML? I've been using it a little bit recently (reading existing documents, not writing my own), and it just seems like a more overcomplicated and less human-readable version of JSON? With potential security vulnerabilities?
> less human-readable version of JSON
Please provide an example, how YAML can be less readable than JSON. I struggle to think of any.
People use YAML because a bunch of other people use YAML. Whatever its warts, there's no use resisting it.
> it just seems like a more overcomplicated
Because people LOVE overcomplicated shit. You see it happen everywhere.
There’s lots of overengineered features in YAML that are problematic, but at a high level, it’s much, much more human-friendly than JSON. And if you love JSON, good news: it’s 100% valid YAML.
Because as long as you stay away from anchors and inline JSON, YAML is a perfectly workable, structured, human-readable format that supports comments.
If not using any esoteric features, it's more human readable (imo), easier to write, can have comments and has some useful features like different kind of multi-line values. JSON is valid YAML, by the way.