dosubot[bot]

Given the upgrade to DevLake version v1.0.0-beta7@2cc08c7 and the issues you're facing with pull request metrics not populating in Grafana, it's crucial to narrow down the cause. Since Jira and...

All data in the "Tag Set" for RAGFlow comes from user-uploaded external files—specifically XLSX, CSV, or TXT tables with two columns: description and tag. RAGFlow does not automatically extract tag-related...

You're right—`z.record(z.number(), ...)` doesn't work as expected because JavaScript object keys are always strings, so Zod can't validate them as numbers at runtime. Even if you use `z.coerce.number()` as the...

There’s currently no official documentation or built-in workaround for the 'block-discussion' component not displaying correctly below 935px. The docs don’t mention any responsive breakpoints or known issues for 'block-discussion' or...

Hi @7H3XXX! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the plate team. This is likely caused by a breaking change in Plate 51.x+: all static rendering features (like `PlateStatic`, `serializeHtml`, etc.) must...

Thanks for confirming the repro. Plate 52.x is ESM-only and adds React Compiler support, so Next.js 16 projects must update their next.config.js to transpile all platejs packages for source maps...

This is a known regression in Plate 52.x with Next.js 16—static rendering and source map errors like what you’re seeing are tracked in several issues and discussions. All the documented...

Hi @gaoyouAwait! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the pro-components team. DragSortTable 目前不支持 tree 格式数据的跨级拖拽。它只支持对扁平数据进行行排序，所有官方文档、示例和源码都没有对树形结构或跨父节点拖拽的支持，相关 issue 和维护者回复也明确说明了这一点，尝试用 DragSortTable 实现树形跨级拖拽会遇到不可控或不支持的问题[[issue 7939](https://github.com/ant-design/pro-components/issues/7939)][官方源码](https://github.com/ant-design/pro-components/blob/f949426ca301c2a6db29a25a49784ab8980ff10d/src/table/components/DragSortTable/index.tsx)。 如果你需要类似 antd Tree 组件的跨级拖拽，建议直接使用 antd 的 Tree 组件（支持 `draggable` 和 `onDrop`...

Hi @PudgeJ! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the pro-components team. 你反馈的 EditableProTable 配合 Form.Item 性能问题，确实是组件架构上的已知限制：当表格数据发生变更时，所有可编辑行的 renderFormItem 都会被重新执行，导致每次编辑都会触发全表格的 re-render，尤其在行数较多（如 15 行以上）时非常卡顿。即使用 React.memo 也无法避免，因为 onChange 等 props 每次都是新引用，所有行都会重新渲染，这是当前实现下无法彻底解决的问题，适合行数较少的场景[详细分析](https://github.com/ant-design/pro-components/issues/9163)。 根本原因在于 EditableProTable 被包裹在 Form.Item...

Hi @sunshineLing! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the pro-components team. 这是已知的 ProLayout 行为限制：在 `layout: 'mix'` 且 `splitMenus: true` 时，顶部菜单只显示一级菜单，左侧菜单显示其余菜单。当你点击二级或三级菜单时，如果当前路由没有对应的子菜单，左侧菜单会消失，这是默认实现，并不是最近的 bug，也没有近期 PR 修复这个问题[[#7833](https://github.com/ant-design/pro-components/issues/7833)][[#3098](https://github.com/ant-design/pro-components/issues/3098)]。 要实现更复杂的菜单联动（比如顶部显示多级菜单，左侧始终有内容），需要自定义菜单渲染。官方推荐用 `menuDataRender` 或 `menuRender`，比如通过给菜单数据加自定义属性（如 `topMenu: true`），然后分别渲染顶部和侧边菜单。示例代码： ```tsx const...