Skip to content
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

Add 'searchKey' to Combo #11532

Closed
radomirchev opened this issue May 11, 2022 · 1 comment · Fixed by #11841
Closed

Add 'searchKey' to Combo #11532

radomirchev opened this issue May 11, 2022 · 1 comment · Fixed by #11841
Assignees
Labels
combo 🧰 feature-request ✅ status: resolved Applies to issues that have pending PRs resolving them, or PRs that have already merged.

Comments

@radomirchev
Copy link
Contributor

Please add a "searchKey" input to the IGX Combo component which tells the combo which data key to use to search/filter by. Right now the search automatically uses the "displayKey" to search and filter the drop down options. However, if you are using custom templates for displaying drop down items in the combo, you might have additional info you'd like to include in the search. By providing a "searchKey" (which defaults to the displayKey value) you can have the search filter by a different data key value which might have more information.

Additional context

Example: I have combo using an array of employee data. The employee data array consists of objects with id, name, division, name_and_division. The "displayKey" is set to "name". I have a custom template to display which prefixes the employee's division to their name (i.e. "Corporate: John Doe"). I'd like to be able to type "corporate" in the search field and have it also match employees at corporate by searching the "name_and_division" property values instead of the just the "name" property. Then when I select an employee, just their "name" appears in the input field box and not their "name and division".

@github-actions
Copy link

There has been no recent activity and this issue has been marked inactive.

@github-actions github-actions bot added the status: inactive Used to stale issues and pull requests label Jul 11, 2022
@Lipata Lipata removed the status: inactive Used to stale issues and pull requests label Jul 11, 2022
@Lipata Lipata added ✅ status: resolved Applies to issues that have pending PRs resolving them, or PRs that have already merged. and removed 🆕 status: new labels Jul 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
combo 🧰 feature-request ✅ status: resolved Applies to issues that have pending PRs resolving them, or PRs that have already merged.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants