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

Suggestion: Switch from yaml to json5 for configuration #5

Closed
jbergens opened this issue Apr 17, 2019 · 1 comment

Comments

Projects
None yet
2 participants
@jbergens
Copy link

commented Apr 17, 2019

Yaml does not seem to be that great, there are still many edge cases, it can be hard to edit if the file is large or without editor support and it is less common than json anyway.

My suggestion would be json5 instead, simplified json and with comments.

https://json5.org/

See here for more info about problems with yaml
https://noyaml.com/

@undefinedbuddy

This comment has been minimized.

Copy link
Member

commented Apr 19, 2019

Your suggestion is appreciated.

  1. "still many edge cases". Please do specify.
  2. "it can be hard to edit if the file is large". The same could be said about JSON5.
  3. "without editor support". Which editors? AFAIK, VSCode, Atom & Sublime Text support YAML by default. As for JSON5, it seems like it's the other way around.
  4. "less common than json". True, but how does that make YAML less suitable (in our case)?

For now, we intend to stick to YAML. Perhaps this is something we might develop a plugin for given that enough users request it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.