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

YAML -> JSON or JSON -> JSON? #10

Closed
ngokevin opened this issue Sep 22, 2016 · 4 comments
Closed

YAML -> JSON or JSON -> JSON? #10

ngokevin opened this issue Sep 22, 2016 · 4 comments

Comments

@ngokevin
Copy link
Member

ngokevin commented Sep 22, 2016

Should the registry be maintained as YAML or JSON?

YAML is indent-based and cleaner to read (without all the double-quotes). Might make it marginally easier to maintain.

Either way, we will still have a build step and still output to JSON.

@fernandojsg
Copy link
Member

I don't really care about one or another, but maybe js devs are more used to use json over yaml?

@ngokevin
Copy link
Member Author

Stayed with YML for now...might be less error prone (forgetting a quote, extra commas, etc0

@dmarcos
Copy link
Member

dmarcos commented Sep 26, 2016

YML means compilation, more tooling, more moving pieces, more formats... I would stick with JSON. It's already pretty legible and easy to edit. I think the marginal gains that YAML brings are not worth the complexity

@ngokevin
Copy link
Member Author

We distribute JSONs so there's no difference to consuming applications.

On the backend/registry side, there's a build/compilation step regardless. The YAML conversion part of that is 1LOC: https://github.com/aframevr/aframe-registry/blob/master/scripts/build.js

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants