fix(sqllab): Reduce flushing caused by ID updates #34720
Merged
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.
SUMMARY
When using the improved SQLLab persistence mode, an ID value is initially generated to manage the tab in localStorage when the tab is created. After syncing with the server, this ID is immediately replaced with the server’s tabViewId, and subsequent data synchronization uses this new ID. Since this ID serves as the key for the SQLLab tab, updating the value causes React to treat it as a new tab, resulting in the component being re-rendered.
To solve this issue, we now preserve the ID for the duration of the session and additionally store the tabViewId. We have modified the system to use tabViewId specifically for data synchronization, which resolves the problem of tab flushing.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
Before:
before-query-editor-id-by-tab-id.mov
After:
after--query-editor-id-sync.mov
TESTING INSTRUCTIONS
Create a new tab, and then observe that the tab is flushed a few seconds later.
ADDITIONAL INFORMATION