You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With [filter]="true", when setting optionLabel, but not setting filterBy, filtering does not work.
I get the following:
core.mjs:10920 ERROR TypeError: option.toLowerCase is not a function
at primeng-dropdown.mjs:644:58
at Array.filter (<anonymous>)
at ComputedImpl.computation (primeng-dropdown.mjs:644:32)
at ComputedImpl.recomputeValue (core.mjs:2646:29)
at ComputedImpl.onProducerUpdateValueVersion (core.mjs:2632:14)
at ComputedImpl.producerPollStatus (core.mjs:2541:14)
at Watch.consumerPollProducersForChange (core.mjs:2454:26)
at Watch.run (core.mjs:2844:49)
at core.mjs:12695:38
Estoy observando algo similar en mi proyecto de trabajo. Mi componente p-drowndown no está realizando el filtrado al establecer filterBy="clave,nombre", solo aplica un filtrado, no el filtrado multiple.
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?
Please don't forget to add your feedback as a comment after reopening the issue. These will be taken into account by us and will contribute to the development of this feature. Thanks a lot for your understanding!
Describe the bug
With
[filter]="true"
, when setting optionLabel, but not setting filterBy, filtering does not work.I get the following:
which again points to the second-last line of
Reproducer
https://stackblitz.com/edit/github-m9lde8?file=src%2Fapp%2Fapp.component.html
Angular version
16.2.2
PrimeNG version
16.9.1
Build / Runtime
Angular CLI App
Language
TypeScript
Node version (for AoT issues node --version)
20.10.0
Browser(s)
Chromium
Steps to reproduce the behavior
In previous versions, when providing "optionLabel" to the dropdown, the filter would work as expected.
In the current version, I have to provide "filterBy" explicitly (set to the same property name) to get the expected behavior
Even when "filterBy" is set, the "emptyFilterMessage" does not show up (neither does it's default, nor the "emptyfilter" pTemplate)
Expected behavior
The filter function should fall back to comparing the same value that is being used to display the label.
The text was updated successfully, but these errors were encountered: