get_code_connect_map (MCP): silent empty map is indistinguishable from wrong fileKey / timeout — return distinguishable errors
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 1-2 天
- 新手友好度
- 45/100
- Issue 类型
- 功能
- 描述清晰度
- 描述清楚
- 活跃度
- 冷清
- 技术栈
- typescript
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
Feature request
get_code_connect_map (Figma MCP) currently returns an empty map {} with success semantics in at least three distinct situations:
- 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
{}. - The node genuinely has no mappings. Response: bare
{}. - 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
statusfield 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).
- 主要语言
- TypeScript
- 星标
- 1.6k
- 派生
- 126
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
figma/code-connect 的其他 Issue
-
normalizePropName strips `#` characters from Figma property names instead of only the `#id` suffix未关闭
难度 2/5 1-3 小时 新手友好度 72/100
figma/code-connect#419 ·
-
feature request
难度 2/5 1-3 小时 新手友好度 66/100
figma/code-connect#403 ·
-
feature request
难度 5/5 一周以上 新手友好度 38/100
figma/code-connect#414 ·
-
feature request
难度 4/5 3-5 天 新手友好度 48/100
figma/code-connect#413 · 1 条评论 ·
-
feature request
难度 4/5 3-5 天 新手友好度 54/100
figma/code-connect#412 · 1 条评论 ·
查看 figma/code-connect 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
vercel-labs/ui#540 ·
维护者通常 1 天内回复
-
accepted ai-dev ai-implementing
难度 2/5 1-3 小时 新手友好度 74/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
-
Negative values skip k/M abbreviation and medium decimal format on line, stacked-area, and tooltip未关闭
难度 2/5 1-3 小时 新手友好度 84/100
britecharts/britecharts#1255 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 70/100
jeanibarz/knowledge-base-mcp-server#1268 ·
维护者通常 1 天内回复