I would to suggest adding a Summary to show up after each run, as it helps to find out if there was any errors, how many stuff was touched, etc.
Specially in long runs where it may error in the middle and user may miss it(due to long scroll), and with summary in the end it may warn for some issues with the config, connection errors, total posters downloaded vs uploaded to Plex, etc...
Example can be seen on a Kometa run, where in the end it shows a summary of what was done.
Maybe make use of Rich's table, create a dataclass obj that stores the uploaded/failed for each media-type for each service, store and count as you go then at the end parse it to a table and print...
Keep doing your good work! Cheers!
I would to suggest adding a Summary to show up after each run, as it helps to find out if there was any errors, how many stuff was touched, etc.
Specially in long runs where it may error in the middle and user may miss it(due to long scroll), and with summary in the end it may warn for some issues with the config, connection errors, total posters downloaded vs uploaded to Plex, etc...
Example can be seen on a Kometa run, where in the end it shows a summary of what was done.
Maybe make use of Rich's table, create a dataclass obj that stores the uploaded/failed for each media-type for each service, store and count as you go then at the end parse it to a table and print...
Keep doing your good work! Cheers!