Fix: filterFields input is not applied in MultiSelect filtering#19341
Open
Indragith20 wants to merge 2 commits intoprimefaces:masterfrom
Open
Fix: filterFields input is not applied in MultiSelect filtering#19341Indragith20 wants to merge 2 commits intoprimefaces:masterfrom
Indragith20 wants to merge 2 commits intoprimefaces:masterfrom
Conversation
4 tasks
Contributor
Author
|
Fix for the issue #19342 |
rosenthalj
reviewed
Jan 29, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Issue
filterFields input in MultiSelect was defined in the public API but not used anywhere in the filtering logic.
As a result, providing filterFields had no effect and filtering always relied on the default field (filterBy/ optionLabel / implicit string matching), causing incorrect filtered results.
This leads to incorrect filtering behavior and makes the filterFields API ineffective.
This PR will fix the above issue.