Implement a frontend-like single entity picker #3653
Merged
Conversation
This file contains 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
- Adds a new Composable `SingleEntityPicker` which aims to provide a text input with autocomplete search for entities like the frontend, where you can pick one
…ty IDs - Trim search input so the space automatically added after an IME suggestion is ignored - Also search entity ID but sort those results second, friendly name keeps priority
JBassett
approved these changes
Jul 14, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Adds a new Composable
SingleEntityPickerwhich aims to provide a text input with autocomplete search for entities like the frontend, where you can pick one and easily see which one was picked. This will be useful to have in various places.Replaced the picker in tiles for now as an example of how it would be used to resolve this unsubmitted feature request. I'll follow up with another PR implementing it in more places if this is accepted.
The frontend includes full fuzzy searching which I'm not going to attempt in the first PR, starting with a search based on friendly name and entity ID, sorting results based on friendly name starts with > entity ID starts with > friendly name to hopefully show the most relevant results first while not requiring an exact match.
Screenshots
Link to pull request in Documentation repository
n/a
Any other notes