You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When searching for a value within the data editor, a list of matches is generated. When we replace one of these values (or make any other change to the editor while the search dialog is up), the list of matches is regenerated from scratch. We should instead just modify the original list of matches when needed.
How will this feature improve this extension
Currently, when we search our place a single entry the query is recomputed for the whole data set. This is computationally inefficient. It creates a noticeable lag when editing a large data set.
Describe alternatives you've considered
Another way to potentially increase the computational efficiency of search and replace is to only search over a part of the data set rather than the whole thing. This comes with some disadvantages and probably shouldn't be done as an alternative to the suggestions made here if it is done at all.
The text was updated successfully, but these errors were encountered:
Describe the new feature being added
When searching for a value within the data editor, a list of matches is generated. When we replace one of these values (or make any other change to the editor while the search dialog is up), the list of matches is regenerated from scratch. We should instead just modify the original list of matches when needed.
How will this feature improve this extension
Currently, when we search our place a single entry the query is recomputed for the whole data set. This is computationally inefficient. It creates a noticeable lag when editing a large data set.
Describe alternatives you've considered
Another way to potentially increase the computational efficiency of search and replace is to only search over a part of the data set rather than the whole thing. This comes with some disadvantages and probably shouldn't be done as an alternative to the suggestions made here if it is done at all.
The text was updated successfully, but these errors were encountered: