Skip to content

[mentions] Property filterOption does not support false value #4366

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.

Sign up for GitHub

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

Jump to bottom
Closed
1 task done
mehunk opened this issue Jul 14, 2021 · 1 comment
Closed
1 task done

[mentions] Property filterOption does not support false value #4366

mehunk opened this issue Jul 14, 2021 · 1 comment
Assignees
@John60676
Labels
2.x for 2.x Accept You are right, we should do that outdated

Comments

@mehunk
Copy link
Contributor

mehunk commented Jul 14, 2021 •
edited
Loading

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

Version

2.2.2

Environment

Mac 11.4, Chrome 91, Vue 3

Reproduction link

Edit on CodeSandbox

Steps to reproduce

Property filterOption does not support false value

What is expected?

Property filterOption supports false value normally by the document

What is actually happening?

Error message occurs in console.
[Vue warn]: Invalid prop: type check failed for prop "filterOption". Expected Function, got Boolean with value false.
@John60676 John60676 added 2.x for 2.x Accept You are right, we should do that labels Jul 14, 2021
John60676 added a commit to John60676/ant-design-vue that referenced this issue Jul 15, 2021
@John60676
refactor(vc-mentions): update types vueComponent#4366
b19c602
@github-actions
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 Jul 16, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@John60676 John60676

Labels
2.x for 2.x Accept You are right, we should do that outdated
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mehunk @John60676