Describe the feature idea
Currently the StoreBackend hardcodes github.com in a number of places, but it would be helpful to be able to also support plugins hosted at other locations. I feel like this could be mediated by having a "github.com" handler for everything that is currently in there that acts based on a URL that starts with "https://github.com", while having different handlers for other sources such as gitlab, or file:// (my desired feature).
It looks like this could be implemented with handlers per URL based on a runner class that holds implementations for the necessary process callbacks:
- self.prepare_plugin
- self.prepare_icon
- self.prepare_wallpaper
- self.prepare_sd_plus_bar_wallpaper
And instead of mapping to a single process function, mapping from a set of process functions in the prepare_tasks step of process_store_data based on URL.
Additional context
No further context right now
Reactions are currently unavailable
Describe the feature idea
Currently the StoreBackend hardcodes github.com in a number of places, but it would be helpful to be able to also support plugins hosted at other locations. I feel like this could be mediated by having a "github.com" handler for everything that is currently in there that acts based on a URL that starts with "https://github.com", while having different handlers for other sources such as gitlab, or file:// (my desired feature).
It looks like this could be implemented with handlers per URL based on a runner class that holds implementations for the necessary process callbacks:
And instead of mapping to a single process function, mapping from a set of process functions in the prepare_tasks step of process_store_data based on URL.
Additional context
No further context right now