-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Component: MultiSelect - Filter not working for grouped items #14278
Comments
This problem persists in v17. |
I updated the issue, because it also applies to |
Same problem with Dropdown component: filter doesn't work without explicit set PrimeNg version: 17.12.0 |
with optionLabel="label" it will filter but group name is not coming along with the label. primeng 17. angular 17. |
Hi, So sorry for the delayed response! Improvements have been made to many components recently, both in terms of performance and enhancement. Therefore, this improvement may have been developed in another issue ticket without realizing it. You can check this in the documentation. If there is no improvement on this, can you reopen the issue so we can include it in our roadmap? Best Regards, |
Describe the bug
When using grouped select items for the MultiSelect component, filtering no longer works, even for SelectItems that have a label property. It is now necessary to explicitly specify
optionLabel="label"
, which is a regression.The same is true for
optionValue="value"
. The whole select item is being emitted, if this is not provided.The problem can be seen in the demo for grouped items on the PrimeNG website: https://www.primefaces.org/primeng-v16/multiselect#group.
PrimeNG versions
16.9.1, 17.0.0
Build / Runtime
Angular CLI App
Language
TypeScript
Steps to reproduce the behavior
SelectItemGroup
that useSelectItem[]
.optionLabel="label"
andoptionValue="value"
and try again. Elements will be found.Expected behavior
When using default SelectItems,
label
andvalue
should not need to be specified as anoptionLabel
resp. anoptionValue
.The text was updated successfully, but these errors were encountered: