KAM
### Description sula目前既然支持了表单的组件容器，是否能考虑新增一个或多种表单布局的组件呢？ 例如较多人使用的tab切换，ant-design中有对应tab的容器组件。当表单中组件达到一定数量时，通过tab能有效区分不同类型表单的分类。 ### Solution 这个是我Mock出来的结构： ```json { "field": { "props": {}, "type": "tab" }, "children": [{ "title": "用户信息", "fields": [ {}, // field {}, // field ] },...
In some scenarios, context.Consumer in React needs to be used. Currently, the plug-in is not exposed to the outside world. What is the reason? When using konva and konva-react, due...
https://github.com/apitable/apitable/blob/4392bce7a85cea3b1a9546b0e69564a25fb5a2d2/packages/core/src/commands_actions/datasheet.ts#L848-L921 行数据删除中，我看逻辑是遍历整个视图中的行，按行顺序去获取OP，我猜测是为了避免OP批量删除中出现删除先后导致下标不准确问题，但是目前的逻辑有考虑过删除通过API调用的方式删除且行ID不按顺序会有问题吗？ 假设行Ids顺序：A、B、C、D、E，删除的API调用为 deleteRecords(["D", "B", "A"])，按照目前的逻辑OP生成的顺序是删除A、B、D的顺序，这跟参数的顺序截然不同，虽然不影响用户体验，但是逻辑上感觉有问题。 而且遍历整个视图的行数据，相比只遍历删除行Ids执行的循环要多，是否可以变成遍历行删除Ids获取对应ID的下标，再处理OP，可以减少了循环次数。
https://github.com/react-component/tree-select/blob/a000435807512c5799292abbd13bfe4649334bae/src/hooks/useFilterTreeData.ts#L40 ```typescript function dig(list: DefaultOptionType[], keepAll: boolean = false): DefaultOptionType[] { function digRecursive(list: DefaultOptionType[], result: DefaultOptionType[]): DefaultOptionType[] { if (list.length === 0) { return result; } const dataNode = list[0];...
Fix the style of the parent header in the fixed part sub-level column scenario under the multi-level header, and adjust the corresponding unit test cases. fix https://github.com/ant-design/ant-design/issues/44974
每次调用 updateOption 在调用链路中都会调用 createSceneGraph，这里的 this.proxy.createGroupForFirstScreen 是否可以做缓存对比来按需更新呢 https://github.com/VisActor/VTable/blob/fb457001fd368191ddf65e44d5b3aeb596b15c4a/packages/vtable/src/scenegraph/scenegraph.ts#L409-L461
### ♻️ Reproduction Steps Scenario: When submitting a task to the server via `new CopilotTask`, an exception occurred during protocol parsing. Upon investigation, it was found that the client submitted...