Open labrys opened 5 years ago
Yes, I agree. Starting as a simple "CouchPotato" equivalent of sabToScikBeard, this script has just had more and more options added to it, with more downloaders, media managers, and features added.
So with a plugin structure, we would have:
is that what you are thinking, or do you have another thought as to how these would be sectioned out?
That's pretty much it in a nutshell
nzbToMedia can be used with a variety of downloaders (e.g. uTorrent, SABnzbd, etc) and media managers (e.g. SickBeard, Radarr, etc) and other utilities for optional functionality (e.g. transcoding, notifications, subtitles, etc). This leads to a large variation in possible configurations.
A plugin structure would separate the code into logical sections to facilitate troubleshooting issues, unit testing, and add-on development.
Additionally if plugins were loaded based only when needed, it would improve stability (bugs in other areas would not affect operation) and efficiency.