stacklok / toolhive-studio / 25735659659

70%

push

github

feat(registry): surface legacy registry format with targeted UI (#2229)

* feat(registry): surface legacy registry format with targeted UI

The backend (stacklok/toolhive#5260) now returns a structured
HTTP 502 Bad Gateway with `code: "registry_legacy_format"` when the
configured custom registry serves data in the deprecated ToolHive format.
Without renderer-side handling the response was treated as a generic
fetch error and the user fell into the catch-all GenericError screen.

This change mirrors the existing `registry_auth_required` and
`registry_unavailable` plumbing:

- Add `isRegistryLegacyFormatError` detector plus the user-facing
  `REGISTRY_LEGACY_FORMAT_UI_MESSAGE` and toast copy (no raw CLI hint —
  desktop users should not see `thv registry convert`).
- Extend `getRegistryErrorToastMessage` so the root `beforeLoad` guard
  redirects to `/settings?tab=registry` with a persistent toast instead
  of letting the error reach `RootErrorComponent`.
- Add a third empty-state branch in `RegistryError` for users who
  navigate directly to `/registry` while the source is misconfigured.

Closes #2228

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* fix(registry): drop CLI/MCP jargon from legacy-format UI copy

REGISTRY_LEGACY_FORMAT_UI_MESSAGE referred to the "upstream MCP format",
which is a CLI/protocol term that desktop users would not recognise.
Rephrase in plain language: the message now says to update the registry
source or reset to default, without naming the destination format.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

4825 of 7593 branches covered (63.55%)

7 of 7 new or added lines in 2 files covered. (100.0%)

7212 of 10507 relevant lines covered (68.64%)

118.87 hits per line