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

Ouverte
  • Quelque chose ne va pas ?
#407 0 commentaires 3 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
1-2 jours
Accessibilité débutants
45/100
Type d'issue
Fonctionnalité
Clarté
Clairement spécifiée
Activité
Calme
Stack technique
typescript
Domaine
api, backend

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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).

Langage dominant
TypeScript
Étoiles
1.6k
Forks
126
Aucune PR mergée en 30 j

Préparer son environnement

Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de figma/code-connect

Toutes les issues de figma/code-connect

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.