f201032137
A list load that failed — a transport error, or a result the SDK's era codec rejects as invalid — reported nothing. The connect-time refresh is fired with no caller to await it (`void this.refresh()`), so its rejection became an unhandled rejection: the header said "Connected", the panel rendered an empty list indistinguishable from a server that has none, and the failed exchange showed in the Protocol panel as a clean success. Two surfaces now tell the truth: - ManagedListState records the failure as observable state (`getError` + an `errorChange` event) and still re-throws, so App's auth-recovery wrapper keeps working. The four `useManaged*` hooks expose it via a shared `useManagedListError`, and the Tools/Prompts/Resources sidebars render a `ListLoadError` alert with the reason and a Retry. - A response the client refused is attributed back to its Protocol entry (`markResponseRejected` → `responseRejected` → `MessageEntry.clientError`), which now renders an Error status and a "Rejected by the Inspector" alert rather than the green resultType badge alone. The SDK gives no request id with a decode failure, so the id is recovered by correlation; see the comment on `markResponseRejected` for why that is exact. Also stops `listAllTools` from dropping a failing excluded-tools walk on the floor — it stays non-fatal but is logged. Closes #1953 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SW1p8E2uiyyLx4RKwrwSrt
57 lines
2 KiB
TypeScript
57 lines
2 KiB
TypeScript
/**
|
|
* ManagedResourceTemplatesState: holds the full resource template list, in sync
|
|
* with the server. A thin subclass of ManagedListState (#1444).
|
|
*
|
|
* Templates have no list-changed indicator of their own — the Resources
|
|
* screen's indicator (driven by `resourcesListChanged`) covers them, and its
|
|
* Refresh re-fetches templates too. So `supportsIndicator` is false: a
|
|
* `resourceTemplatesListChanged` auto-refreshes only when the server opts in
|
|
* via `autoRefreshOnListChanged`; otherwise it does nothing and the user pulls
|
|
* via the Resources Refresh (#1402).
|
|
*/
|
|
|
|
import type { InspectorClientProtocol } from "../inspectorClientProtocol.js";
|
|
import type { ResourceTemplateType as ResourceTemplate } from "@modelcontextprotocol/client";
|
|
import {
|
|
ManagedListState,
|
|
DEFAULT_LIST_CHANGED_DEBOUNCE_MS,
|
|
type ManagedListEventMap,
|
|
} from "./managedListState.js";
|
|
|
|
export interface ManagedResourceTemplatesStateEventMap extends ManagedListEventMap {
|
|
resourceTemplatesChange: ResourceTemplate[];
|
|
}
|
|
|
|
export class ManagedResourceTemplatesState extends ManagedListState<
|
|
ResourceTemplate,
|
|
ManagedResourceTemplatesStateEventMap
|
|
> {
|
|
constructor(
|
|
client: InspectorClientProtocol,
|
|
debounceMs = DEFAULT_LIST_CHANGED_DEBOUNCE_MS,
|
|
) {
|
|
super(client, {
|
|
listMethod: "resources/templates/list",
|
|
changeEvent: "resourceTemplatesChange",
|
|
listChangedEvent: "resourceTemplatesListChanged",
|
|
// Templates are gated on the broader `resources` capability.
|
|
capabilityKey: "resources",
|
|
// No paged counterpart (templates aren't paginated in the UI), so they
|
|
// must still aggregate on connect even in paginated mode (#1721).
|
|
deferWhenPaginated: false,
|
|
supportsIndicator: false,
|
|
debounceMs,
|
|
fetchAll: async (c, cacheMode, metadata) => {
|
|
const result = await c.listAllResourceTemplates({
|
|
cacheMode,
|
|
metadata,
|
|
});
|
|
return result.resourceTemplates;
|
|
},
|
|
});
|
|
}
|
|
|
|
getResourceTemplates(): ResourceTemplate[] {
|
|
return this.getItems();
|
|
}
|
|
}
|