mirror of
https://github.com/Prowlarr/Prowlarr.git
synced 2026-03-02 22:57:22 -05:00
Adding enabled indexer through API requires empty tags array 🤷🏻♂️ #621
Labels
No labels
Area: API
Area: Database
Area: Db-migration
Area: Download Clients
Area: Indexer
Area: Metadata API
Area: Notifications
Area: Tooling
Area: UI
Area: Update API
Priority: High
Priority: Low
Priority: Medium
Status: Cannot Reproduce
Status: Confirmed
Status: Help Wanted
Status: In Progress
Status: Indexer - need invite
Status: Info Needed
Status: Investigating
Status: Logs Needed
Status: Maybe One Day
Status: Needs Triage
Status: Unlikely
Status: Waiting for OP
Status: Won't Fix
Type: Bug
Type: Bug
Type: Documentation
Type: Duplicate
Type: Enhancement
Type: External Bug
Type: Feature Request
Type: Regression
Type: Support
Type: Support.
lidarr-pull
radarr-pull
sonarr upstream
sonarr-pull
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Prowlarr#621
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @PierreMesure on GitHub (Jul 30, 2022).
Is there an existing issue for this?
Current Behavior
I'm using the API to add an indexer. With the following body, I'm able to add a tracker to Prowlarr:
Request:
POST http://<domain>:9696/api/v1/indexerHowever, if I add
"enable": true, I get:(full stacktrace below)
Which gets mysteriously solved if I add
"tags": []. Is there a good reason for this empty array to be needed? Or is it just a bug? In general, I haven't been able to find any logic nor documentation for which fields are required using the API, it's really a game of trial and error.Expected Behavior
The API should have a clear behaviour and the necessary fields should be well documented for each call.
It should probably infer more default values so it doesn't require as many fields. And these values should be consistent with the default that are used when doing the same action through the GUI. For instance,
"enable": trueseems to be the GUI’s default but not the API’s.Regarding this specific call, the
tagsarray should probably default to[]and I would investigate why it is needed only when"enable": true.Steps To Reproduce
Environment
What branch are you running?
Master
Trace Logs?
AB#3405