TheGiddyLimit / plutonium-addon-automation

An interoperability addon which makes Plutonium play nice with automation modules.
https://thegiddylimit.github.io/plutonium-addon-automation/
MIT License
32 stars 7 forks source link

Human-readable list of automated items #77

Open Spappz opened 1 year ago

Spappz commented 1 year ago

Make list of things that have any PAA data attached. Should ideally be auto-generated from the data files as part of the release deployment. Should expose the required and TODO arrays.

Current idea is to actually create a very stripped-down version of 5eT (without service worker?) that just has a single list page, then host it on Github like the conversion tool. This would allow an easily recognisable UI to be levered, with filters for document type, dependencies, completion-state, presence of macro, last-confirmed-stable dnd5e/Foundry versions for macros, etc. Homebrew sources could be included too.

Stretch goal: record which version an item is released in, so one can also filter to 'new additions' or 'additions since [version number]'. I doubt the changelog is going to lits every single item-addition or it'll very quickly get bloated af (compare with "added more PHB spells")

This might all be overkill, though, so just auto-generating a markdown file that the user can CTRL+F through themselves would also work.

revilowaldow commented 1 year ago

IMO, let's just get a markdown file with sections for class, spell, item etc going first, the filters and list page etc sounds like a needless level of complexity.

If you're really keen on it then I'd suggest to instead backport it into the main site as a group of filters based on loading an external index from here. "Has automation" over making an entire pseudo site

Spappz commented 1 year ago

My thought re: complexity was to basically code it once so no one needs to do it again. An example use case would be when a user has prematurely updated Foundry before, say, Active Auras has caught up, and they can't revert. This is a new campaign, though, so they want to just tell players to only import documents that don't require Active Auras for now. Providing an explicit list of those spells by just clicking a couple times is easier than them telling their players "CTRL+F every document you import" or scripting through the JSON themselves.

... In this case, actually, it would be useful to merge the filters with Plutonium's own importer. idk tbh I'm just throwing ideas around; 5eT is there and is known, so it seemed to fit. The exact details of it are kinda irrelevant unless someone complains, I guess.