Skip to content

【表头分组】会影响change中filters和sorters的正确获取(Group will affect the correct acquisition of filters and sorting in change) #7160

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
1 task done
BillEliot opened this issue Dec 5, 2023 · 1 comment · Fixed by #7233
Labels

Comments

@BillEliot
Copy link

BillEliot commented Dec 5, 2023

  • I have searched the issues of this repository and believe that this is not a duplicate.

Version

4.0.7

Environment

fork文档的CodeSandbox环境
(Same CodeSandbox environment as the document)

Reproduction link

Edit on CodeSandbox

Steps to reproduce

  1. 直接复制文档中【自定义筛选菜单】的CodeSandbox.
  2. 修改columns,在原有columns外加一个group.
  3. @change中log出filters,可以发现,filters中只包含当前确认的column,并且,当切换分页时,之前修改的filters丢失,打印filters为空。

(1. Directly copy the CodeSandbox in the [Customized filter panel] in the document.
2. Modify the columns and add a group to the original columns.
3. print the filters in @change and you can find that the filters only contain the currently confirmed columns, and when switching paging, the previously modified filters are lost and the printed filters are empty.)

What is expected?

@change中filters可以正常输出,即切换分页时,filters不为空。
(The filters in @change can be output normally, that is, when switching paging, the filters are not empty.)

What is actually happening?

@change中,切换分页时,filters为空。
(In @change, when switching paging, filters are empty.)

@BillEliot BillEliot changed the title 【表头分组】会影响change中filters和sorters的正确获取 【表头分组】会影响change中filters和sorters的正确获取(Group will affect the correct acquisition of filters and sorting in change) Dec 5, 2023
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 16, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant