Skip to content

feat(settings): show release provider availability - #1532

Open
revam wants to merge 1 commit into
masterfrom
feat/release-provider-availability
Open

revam wants to merge 1 commit into
masterfrom
feat/release-provider-availability

Conversation

@revam

@revam revam commented Nov 16, 2026 •

Copy link
Copy Markdown
Member

Why

A release provider can be ticked for auto-linking and still never be used: it may not be configured (AniDB without credentials), held back by a suspension (an AniDB ban), or, with the new ManualOnly kind on the server, only answer searches a person starts. The first provider to use ManualOnly is the Offline Importer, which cannot match files on its own until an admin adds an auto-match rule to its configuration. Ticking it under the auto-linking providers then does nothing, and nothing in the web UI says why.

GET /api/v3/ReleaseInfo/Provider already reports each provider's Availability, but the web UI showed none of it for release providers. The metadata source settings already show the same kind of status ("Not Configured", "Suspended"), so this follows that pattern.

What

  • Typed the Availability object (Kind, Reason, ResumesAt, SuspendedBy) and added it to ReleaseProviderInfoType.
  • Added a small ReleaseProviderAvailability label shown after the plugin name of each provider:
    • Auto-linking list: "Not Configured" (danger colour), "Suspended" or "Manual Only" (warning colour).
    • Manual linking list: "Not Configured" and "Suspended" only, since a manual-only provider works fine there.
    • The server's Reason is the tooltip, plus "Resumes ..." when a suspension has an end time (same format as the metadata source settings).
    • Available shows nothing. Whether a provider is ticked is the checkbox's job; the server reports availability apart from it, so an unticked provider still shows why it can't be used.
  • No new fetching: saving the providers already invalidates the release-info/providers query, so the labels refresh after a save.

Where

  • src/core/types/api/provider-availability.ts (new): the availability types. Kept generic, since relocation providers carry the same object.
  • src/core/react-query/release-info/types.ts: Availability on ReleaseProviderInfoType.
  • src/components/Settings/ReleaseProviderAvailability.tsx (new): the label.
  • src/components/Settings/HashingAndReleaseSettings/ReleaseSettings.tsx: one line per list rendering the label.

Testing

  • pnpm lint, pnpm tscheck, pnpm build and pnpm test pass.
  • Dev server against a local scratch server (older core, no ManualOnly yet), signed in as a throwaway admin, which was deleted afterwards. No settings were saved.
    • Real responses (only Available from that core): no labels, layout unchanged, no console errors.
    • With a temporary, uncommitted mock of the query giving AniDB Suspended, Offline Importer ManualOnly and another provider NotConfigured: the labels and tooltips render as below, and "Manual Only" is left out of the manual linking list.

Screenshots

Both lists with mocked availabilities:

lists

The tooltip with the server's reason:

tooltip (1)

Feedback wanted

  • Whether the label colours match expectations (danger for not configured, warning for suspended and manual only), and whether the tooltip is enough or the reason should be a visible line.

Relation to feat/split-hashing-release-settings

That unmerged branch moves the provider lists from components/Settings/HashingAndReleaseSettings/ReleaseSettings.tsx into pages/settings/tabs/ReleaseSettings.tsx and removes the HashingAndReleaseSettings folder. To keep the merge easy, the label lives in its own component directly under components/Settings/, and the change to the list is one import plus one line per list. Whichever branch merges second only needs to carry those lines over to the new file.

- Typed the `Availability` the server gives each release provider
- Showed "Not Configured", "Suspended" or "Manual Only" next to an auto-linking provider, with the server's reason as a tooltip
- Left "Manual Only" out of the manual linking list, where such a provider works

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant