4 ms·
Write your own is a bad option. I have tried it and found that you end up spending lots of time maintaining a parser. I have found some success in my org using
by mdmglr 4y ago
Write your own is a bad option. I have tried it and found that you end up spending lots of time maintaining a parser.
I have found some success in my org using JSON with JSON Schema [1]. Combine with a json schema aware IDE like VS Code it solves the documentation problem.
[1] https://json-schema.org/ https://json-schema.org/
- gnulinux 4y agoBut article literally makes the same point you're making. They only put "make your own" as the last resort option. Here: > If for some reason a key-value configuration format doesn’t meet your needs, and you can’t use a scripting language due to performance or size constraints, then it might be appropriate to write your own configuration format. But if you find yourself in this scenario, think long and hard before making a choice that will not only require you to write and maintain a parser but also require your users to become familiar with yet another configuration format.