Skip to content
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

TreeSelect Component: How can I take the control of search value? #10910

Closed
1 task
pkl93 opened this issue Jun 14, 2018 · 1 comment
Closed
1 task

TreeSelect Component: How can I take the control of search value? #10910

pkl93 opened this issue Jun 14, 2018 · 1 comment
Assignees
Labels
3.x 3.x stable issue or bug fix, PR should be cherry-pick to master Inactive

Comments

@pkl93
Copy link

pkl93 commented Jun 14, 2018

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

What problem does this feature solve?

The search value will be cleared when I check a option in multiple mode, but in my case I don't want it happen and I can't find a easy way to control this.
In our project, options is too many to choose without search. sometimes I need to search one parent node, and check some children in this. If the above happen, I have to input again.

What does the proposed API look like?

A new prop to control the search value, or just prevent the value being cleared due to checking options in multiple mode。

@pkl93 pkl93 changed the title TreeSelect: Control the input value TreeSelect Component: How can I take the control of search value? Jun 19, 2018
@zombieJ zombieJ added the 3.x 3.x stable issue or bug fix, PR should be cherry-pick to master label Sep 24, 2020
@github-actions
Copy link
Contributor

Hi @pkl93,
Current branch is off the maintenance period. We may not accept pull request or fix bug with it anymore. This topic will be auto closed.

你好 @pkl93,
当前分支已经过了维护期。我们不会再接受对其的相关 PR 与 issue。当前 topic 会被自动关闭。

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3.x 3.x stable issue or bug fix, PR should be cherry-pick to master Inactive
Projects
None yet
Development

No branches or pull requests

4 participants