Use yaml for all configuration

Feature Requests
1

JSON is cumbersome to edit. Yaml is super easy to edit, supports templating and can be used for describing complex data structures while keeping them editable. All configuration like MCP settings, .cursorrules etc should use YAML. Agree?

2

Totally the opposite :slight_smile: yaml is overcomplicated format and json is structured, supports templating and describing complex data structures while keeping them editable.

Hard no on yaml everywhere. Its good that less and less tools use it nowadays. its never been a user or tech friendly format.

1 Like
3

YAML is great for RAG systems - putting together a taxonomy of tags at the top of markdown files before vectorizing is a fantastic strategy for a assembling a knowledge base.

4

hehe frontmatter works for that so well instead of yaml :slight_smile:

No im not totally against yaml, but lets not overcomplicate stuff, json doesnt care about spaces etc. its keys and values or so.

5

would be cool to use txt, markdown, yaml, or json - why not have it all? :laughing:

1 Like
6

I mean, that’s what AI’s for, right? Whatever format they use, it is simple enough to edit with AI. But I agree. I prefer YAML over JSON, but I do use both. I’m heavy into Docker, which is the only reason I know YAML syntax and prefer it. It looks cleaner to me as well, which makes my OCD brain happy :slight_smile: