Added virtualization to DxcSelect
#2243
Draft
+2,307
−3,814
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.
Checklist
(Check off all the items before submitting)
/lib
directory./website
as needed.Our select was not behaving properly with huge datasets due to performance issues (overloading the DOM and doing data processing).
In order to get around that problem, there is a common strategy, virtualization, which allows the component to load only a few items at once and update that list of items each time an user scrolls over it.
I have implemented it using
virtuoso
, one of the highest performance libraries out there that remains up to date and can achieve all the common use cases for these kind of strategies.The work is still in progress, however, there are a few limitations that we have to take into account:
// TODO
in the code.DxcPaginator
menus, which don't allow switching pages smoothly when there is a big amount of them.DxcResultsetTable
component with a simpler logic which could be useful to understand howvirtuoso
works in an easier way.