Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support forceSave For Indexer Update Methods (upd_indexer) #169

Open
2 tasks done
jd4883 opened this issue Feb 24, 2024 · 0 comments
Open
2 tasks done

Support forceSave For Indexer Update Methods (upd_indexer) #169

jd4883 opened this issue Feb 24, 2024 · 0 comments
Labels
type/feature New feature or request

Comments

@jd4883
Copy link

jd4883 commented Feb 24, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Expected feature

Per the API Docs for sonarr, it seems that pyarr does not support adding in the force flag.

Possible Solutions

Can the additional flag be added to the upd_indexer method for all the *arr apps API's be updated to support the forceSave functionality? You should be able to have the class include a default value of false if unset which should not limit any existing functionality but enable this part to work as intended.

Context / Reason

This is useful for some configurations, which if done in the UI give you a warning and then when you resubmit the request it goes through.

As an example, if you set seeders to 0 the API will warn without this flag and cannot be handled via the API without the flag.

Code of Conduct

  • I agree to follow this project's Code of Conduct
@jd4883 jd4883 added the type/feature New feature or request label Feb 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/feature New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant