feat: add BaseSelectNative component #3169
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
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.
This PR adds a new vendor component:
BaseSelectNative. For the time being, this component is only used inFullPaginator.Mature component libraries tend to have multiple flavors of select components to choose from. For example, a subsequent PR will add a
BaseSelectAsynccomponent which allows you to search for the option (ie: a user to send a message to).BaseSelecthas highly-customizable UX, but has slow rendering performance on lists that have potentially hundreds of options.BaseSelectNativerenders options very quickly, with the trade-off of having virtually no customizable UX for the select options.Before
After
