[Fix-4574][web] Prevent repeated project tree refresh - #4575
Open
gordan-zhang wants to merge 1 commit into
Open
Conversation
Co-authored-by: Cursor <cursoragent@cursor.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Purpose of the pull request
Prevent the Data Studio project tree from entering a repeated refresh loop after the toolbar refresh button is clicked.
Closes #4574.
Brief change log
PROJECT_REFRESHaction immediately after dispatching the catalogue tree refresh.datafrom retriggering the same action and requestinggetCatalogueTreeDataindefinitely.Verify this pull request
This change is not covered by automated UI tests and was verified as follows:
prettier --check src/pages/DataStudio/Toolbar/Project/index.tsxgit diff --checkdatacan no longer re-enter thePROJECT_REFRESHbranch because the action is cleared.The repository-wide TypeScript check currently reports pre-existing dependency and generated-module errors after a lockfile-free install; no new error is associated with this change.