MCP/REST: request id in successful answers, file names without spaces

未关闭
#481 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
58/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
javascript, react
领域
api, backend

调研方向

Start by locating the MCP and REST response code and the code that derives the saved filename. Check how successful answers and errors currently carry request IDs, and where the REST header is set. Add the ID to successful structured content and the REST body, and slug the filename while keeping the title as the download display name; verify both behaviors with the relevant tests.

由索引模型根据 Issue 内容生成。

描述

area:mcp area:server enhancement

Two small things a test client noticed in three runs against the dev stack:

  • Successful MCP and REST answers carry no request id (errors do, and REST has the X-Request-Id header). A client that later reports "this answer looked wrong" has nothing to give the operator to find the log line. I want the request id in every answer's structured content (and REST's body), kept short.
  • The saved file name comes from the title with spaces (Umsatz pro Produkt.json). Links and shells handle that worse than umsatz-pro-produkt.json. Check how filename is derived and whether a slug (keeping the title for the download's display name) is better.
主要语言
JavaScript
星标
1
派生
1
平均合并
3 小时 34 分钟
30 天内合并 PR
213

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

eizedev/pivotkit 的其他 Issue

查看 eizedev/pivotkit 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。