Closed 3vorp closed 7 months ago
After a lot more thinking, I've decided this can function as three separate JSON files, much like how textures work.
packs.json
would simply have basic information about each pack — GitHub urls, display names, pack tags, etc
submissions.json
would have submission-related information, using a similar interface to the current submission setup in settings.json
projects.json
(no idea what to call this) would have the syntax specified in https://github.com/Faithful-Resource-Pack/API/issues/40
Like this, projects.json to be defined
Cool, my thinking with having submissions.json
separately stored is that the submission bot would have minimal breaking changes since the interface wouldn't change.
Decided to simplify my life and move projects.json
into the actual texture db itself, see #39 for more info on that
Currently,
settings.json
stores a bunch of information about various resource packs. I was thinking that consolidating all that stuff into a singlepacks
collection would make a lot more sense, since it's already structured data with known keys (the submission pack interface is usable as-is, it's basically a collection within a collection as it stands).Existing information that could be combined would include:
settings.json
fields)16x packs could be stored in addition to Faithful packs here by simply having a boolean flag to enable submissions for a given listed pack. This way, one could support an arbitrary number of packs simply by registering a new one in the packs collection and modifying a few TypeScript interfaces.