Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is YML a better choice for configuration file? #69

Open
haojianzong opened this issue Aug 12, 2021 · 2 comments
Open

Is YML a better choice for configuration file? #69

haojianzong opened this issue Aug 12, 2021 · 2 comments
Labels
enhancement New feature or request

Comments

@haojianzong
Copy link

haojianzong commented Aug 12, 2021

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

@haojianzong haojianzong changed the title Is YML a better choice for configuration? Is YML a better choice for configuration file? Aug 12, 2021
@haven2world
Copy link
Collaborator

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.

@imWildCat
Copy link
Contributor

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

@imWildCat imWildCat added the enhancement New feature or request label Aug 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants