Nanoware/Terasology

Sort out that idea about a type "middle" extension for .json

Cervator opened this issue · 3 comments

I think we might have gotten away from this a bit, but I came across a reference that reminded me.

Idea is doing something like so:

dirt.block.json
mainmenu.ui.json
portal.prefab.json
... etc

Those are likely poor examples thrown together real quick, but we have a lot of .jsons that could be more specific. If we want to go for that we should be applying it during TGC

I don't like the idea of middle extensions. Either we just do .json, or we use a different extension for each type (.block, .style, .prefab). Probably the latter? Easy enough to do anyway, and we can tackle this during TGC, certainly.

That works too - the .json at the end would be mainly for tools to recognize as text / grab the right highlight, but I'm figuring IntelliJ and other IDEs will do that automatically anyway. Or we can auto-magic some extension associations.

Want to consider an exact convention for the types we've currently got? Sounds architectural :-)

Completed by @immortius - closing as complete :-)