Low-complexity but powerful importer/sources variants about cartridges HOT 1 CLOSED

Hi!
Thanks for the proposal.

Currently, Cartridges does not have a clearly defined way of importing games, other than setting variables and calling functions in a specific instance of a class. While this does make the code more messy, it also makes it more adaptive as any function or class can act as an importer as long as it calls the right functions and sets the right variables. The function itself can be asynchronous, it can run multiple times, etc.
As such, I don't think refactoring the current import sources would need to be a priority. For sources that have a url handler, I think one file and one function would be enough, but it doesn't really matter. Multiple files could work just as well and I would not be against copying code from Gali that's using that structure as importers themselves are mostly self-contained.
Regardless, I would like if we could talk this over on Discord sometime!

from cartridges.