Skip to content

fix: 接口文档内容不一致 #1505

Closed
Closed

Description

@lulg

Pre-submission checklist | 提交前检查

  • I have searched existing issues and this hasn't been mentioned before | 我已搜索现有问题,确认此问题尚未被提及
  • I have read the project documentation and confirmed this issue doesn't already exist | 我已阅读项目文档并确认此问题尚未存在
  • This issue is specific to MemOS and not a general software issue | 该问题是针对 MemOS 的,而不是一般软件问题

Bug Description | 问题描述

我自己部署好后用/docs看到的参数是这样的:

Image 但是官方文档上描述的是这样的: Image

希望能规范统一一下。

How to Reproduce | 如何重现

用的最新发布版。使用http://host:port/docs访问api文档

Environment | 环境信息

Docker安装,精简包

Additional Context | 其他信息

No response

Willingness to Implement | 实现意愿

  • I'm willing to implement this myself | 我愿意自己解决
  • I would like someone else to implement this | 我希望其他人来解决

Activity

  1. MaiHHConnect commented on Apr 21, 2026

    @MaiHHConnect
  2. lulg commented on Apr 21, 2026

    @lulg
    Author

    💬 我也在做记忆系统相关的工作:CausaMem,可以来看看,说不定有能借鉴的地方 🙂

    别到处打广告了,真的很烦。你那玩意真得好用也不至于只有3星。你先搞出几个案例来给大家瞧瞧。

  3. changed the title [-]接口文档内容不一致[/-] [+]fix: 接口文档内容不一致[/+] on Jul 1, 2026
  4. self-assigned this
    on Jul 1, 2026
  5. added and removed
    types:bugSomething isn't working | 功能异常
    area:coreMOS 编排层 / 框架底座 / 跨模块问题
    on Jul 7, 2026
  6. added theissue type on Jul 7, 2026
  7. added
    status:readyReady for implementation; waiting for assignee or AI dispatch | 可进入实现,等待认领或派发
    on Jul 8, 2026
  8. added a commit that references this issue on Jul 16, 2026
    2c60267
  9. shinetata commented on Jul 16, 2026

    @shinetata
    Collaborator

    已在 #2112 修复,并合入 dev-v2.0.24。

    原因是 /docs 里 Swagger UI 对 messages 的 str | MessageList | ... 联合类型取了第一个分支,把示例渲染成了 "string"。现已通过模型级 OpenAPI example 展示结构化 messages 列表,与官方文档对齐。将随该分支后续发版生效。

    感谢反馈!

  10. added a commit that references this issue on Jul 19, 2026
    bedc187
  11. added a commit that references this issue on Sep 18, 2026
    73580c5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

area:docs文档、示例status:readyReady for implementation; waiting for assignee or AI dispatch | 可进入实现,等待认领或派发

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions