YAML -> JSON or JSON -> JSON?

aframevr / aframe-registry

[DISCONTINUED] Curated collection of community A-Frame components.

https://aframe.io/registry/

MIT License

77 stars 39 forks source link

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

Closed ngokevin closed 8 years ago

ngokevin commented 8 years ago

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 commented 8 years ago

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

ngokevin commented 8 years ago

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

dmarcos commented 7 years ago

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 commented 7 years ago

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