Create SearchInteractiveWithDebounce.razor #396
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
|
The txt file is created and updated automatically |
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.
Pull Request
📖 Description
Based on discussion with @vnbaaij here: #389. Tested the component with 6000 values and it works really well. If you can get the results down to around 500 after first search (two letters in my test values) there is no lag at all.
Do I need to create examples/FluentUI.Demo.Shared/wwwroot/sources/SearchInteractiveWithDebounce.razor.txt or is that file normally added automatically later? If it is not created automatically does it need to be updated every time an example is updated?
✅ Checklist
General
Component-specific
⏭ Next Steps