Hi, I’m writing a Download client integration for Sonarr and will submit it as a pull request but I want to ask a question about the inner workings of Sonarr before I submit it so I keep things in keeping with standards?
Is there a recommended way to persist data between restarts? The download client I’m writing for doesn’t have an api to list it’s current queue, I can get the status of a job by passing in the job id so need to store a list of job id’s started by Sonarr for later retrieval, I’m currently using a singleton class but this won’t survive a Sonarr restart.
If I add more functionality at a later date and change or add items on the download clients settings page, how can I prevent this from breaking someones existing setup?