fix: filterOption for transfer shouldn't depend on filterValue #39906 #39907
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
|
afc163
added a commit
that referenced
this pull request
Dec 30, 2022
yoyo837
pushed a commit
that referenced
this pull request
Dec 31, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
[中文版模板 / Chinese template]
🤔 This is a ...
🔗 Related issue link
See #39906
https://codesandbox.io/s/antd-reproduction-template-forked-jyh2k9?file=/index.js
💡 Background and solution
filterOption prop of the Transfer component should be triggered regardless of whether something is entered into the search input.
📝 Changelog
No changelog needed.
☑️ Self-Check before Merge