The idea is to adapt series plugin so that followed series (and all settings for them) can be controlled via the db (and thus via api) rather than just in the config.
Replace (upgrade) internal series plugin Series model to include all the settings fields, similar to model in PR:1228, also have a default list, and named lists of series.
Have a new configuration for the series filter plugin, which allows specifying one of the db series lists, rather than listing series directly in the config file.
API/CLI etc. are then used to control the series and settings in the named series lists.
The current Series db model gets updated from the config each time a task is run, so that things like series CLI work. How do we adapt that to new system? What named series list would the go in?
Answer: A default series list will be updated via the config on each task run. We'll also seperate series-tracking
capabilities and series-list
ones via API/CLI.
Is there a way to change settings for a whole db list? Or are they always stored per series?
Answer: Yes, series_list
can be changed globally via API/CLI.
configure_series, Does it write a list to db, or pass a text config to series plugin still?
Answer: Writes to series_list
with a default name, does not deletes values from it, just marks relevant ones as active
(similar to how we currently use in_task
).
default_series_list
for example).next_series_episodes
will be able to take a series_list
name. By default it'll use the default series name.configure_series
will still be used and will reset the default list. Behind the scenes it'll add new values to list and mark them as active
. All other values in the list will be marked as non active. Series filter will take only active
series to consideration.tvdb_id
, trakt_show_id
, etc.)