feat(scaffolder): use virtualization with MultiEntityPicker #25315
+45
−2
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.
Hey, I just made a Pull Request!
Use virtualization with MultiEntityPicker. This fixes performance issues with large data sets. Fixes #25243.
Testing
Not sure how you would test this with
testing-library
as the issue manifests itself only in real browser environment. However have tested this locally by comparing behaviour betweenmaster
branch and this as follows:catalog-info.yaml
containing a large number (~5k will do it) of entities using a script like so:yarn dev
and wait until all entities have been ingestedCustom Field Explorer
from http://localhost:3000/create/edit and selectMultiEntityPicker
master
branch browser (tested with latest Chrome) quickly becomes unresponsive and finally hangs:I have tested this with 5k, 10k and 100k entities and in all cases the input remains responsive. Here's demo with 100k entities
Screen.Recording.2024-06-19.at.12.57.22.mov
✔️ Checklist
Signed-off-by
line in the message. (more info)