Organize json files into directories about browser-compat-data

[teoli2003]

Mmh, I have some doubt here. For API, we have 1 file per interface, named <interface_name>.json. It is trivial to find the right face for updating it (or to create it). Having directories per API forces us to know the API it relates to, and this is non trivial.

For example this is the difference between the way Gecko stores .webidl files: they are in one single directory and easy to find. Blink, put them in directories, and finding the right one is always difficult.

I would propose not to do this.

[a2sheppy]

I mostly agree, although there would be times it would be nice to have a way to quickly grab the all of the JSON for a specific API. Perhaps some sort of a catalog of the JSON files for each API? Hm. Eric Shepherd Senior Technical Writer, MDN MDN: https://developer.mozilla.org/ Blog: https://www.bitstampede.com/ On October 3, 2017 at 8:33:31 AM, Jean-Yves Perrier ( [email protected]) wrote: I would propose not to do this.

[Elchi3]

Perhaps some sort of a catalog of the JSON files for each API? Hm.

Over in #233 we agreed that this catalog is actually what we have as groupdata.json so far and the plan is that a polished groupdata will live in the mdn/data repository one day.

I agree with what Jean-Yves said.