Open haojianzong opened 3 years ago
I think we can support both? But we'd better keep JSON, for many front-end engineers, they're more familiar with JSON and maybe have no idea what yml is.
yaml
is also good.
I think we can find a way to support both yaml, json and even TypeScript (example).
IMO, these configuration files are portable to difference languages. For example, https://github.com/spf13/viper is a Golang configuration solution for
JSON, TOML, YAML, HCL, envfile and Java properties config files
Currently we are using JSON, but YML requires less characters and is easier to modify in CLI. What do you think?
Example from a similar code generator lib: https://github.com/krzysztofzablocki/Sourcery/blob/master/SourceryTests/Stub/Configs/multi.yml