get_code_connect_map (MCP): silent empty map is indistinguishable from wrong fileKey / timeout — return distinguishable errors

Aperta
  • Qualcosa non va?
#407 0 commenti 3 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
1-2 giorni
Idoneità per principianti
45/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Tranquilla
Stack tecnologico
typescript
Ambito
api, backend

Direzione di ricerca

Start by tracing the get_code_connect_map MCP tool and how it represents empty results and lookup timeouts; the issue names no files or tests. Identify where the file lookup and timeout outcomes are handled, then add distinguishable machine-readable results or errors for those cases while preserving a genuine empty map. Done means MCP clients can tell all three outcomes apart; add or update coverage for each case.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Feature request

get_code_connect_map (Figma MCP) currently returns an empty map {} with success semantics in at least three distinct situations:

  1. The queried fileKey has no published Code Connect — typically because the caller passed the fileKey of a design file that instantiates the components, rather than the library file the mappings were published against. Response: bare {}.
  2. The node genuinely has no mappings. Response: bare {}.
  3. The backend lookup timed out — e.g. when the queried node is too broad (page/document root on a large file). Response: {} plus only a prose note appended to the result: "Note: the Code Connect lookup timed out, so this response may be missing Code Connect data." (reproduced 2/2).

For MCP clients — especially agents — 1 and 3 are indistinguishable from 2. The practical failure mode is an agent confidently concluding "this component has no Code Connect mapping" and writing that into downstream code or docs, when the mappings exist and the call was merely mis-scoped or timed out. Since passing a design-file key is the natural first attempt (it's the fileKey the caller is holding), case 1 is the default path for anyone who doesn't already know the library fileKey.

Request: make the outcomes distinguishable. Any of these would work for MCP clients:

  • an error (or MCP tool error result) for "this file has no Code Connect published" and for "lookup timed out", or
  • a machine-readable status field alongside the map (ok / no_code_connect_for_file / timeout_partial), keeping {} only for a genuine empty result.

Scope note: I'm aware #284 was routed away as an MCP-server issue, but #373 (MCP response shape) was fixed via this repo, so filing here for the paper trail — happy to move this to the right channel if there is one.

Related, not duplicates: #340 (MCP silently ignores Angular mappings), #292 (placeholder snippets), forum threads 42405 and 56495 (empty/partial maps with different root causes — those are about missing entries, this one is about failure modes being unsignaled).

Lingua principale
TypeScript
Stelle
1.6k
Fork
126
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di figma/code-connect

Tutte le issue di figma/code-connect

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.