Skip to content

u-select-entity/u-select-multiple debouncedFetch replaced with throttledFetch

Chernykh Denys requested to merge fix/u-select_debouncing into master

In some cases u-select-entity/u-select-multiple controls may show irrelevant data because of debouncing. When a user changes the query text on the control there is a time gap (currently 600ms) before the fetch is actually completed. If the control has already fetched options, it shows them, waits 600ms and only then refreshes the options. If the previously fetched options belong to another entity we will see them before refresh.

On the other hand throttling allows to get relevant options, wait some time and then repeat fetching if a user has managed to modify query text.

There is an appropriate bug ticket: LDOC-1275

Merge request reports