[AMORO-3371] Slow Display of Table List in Amoro Interface (#3371) #3372
Conversation
This file contains 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
zhoujinsong
approved these changes
Dec 20, 2024
There was a problem hiding this comment.
I tested it in my local environment and found these changes:
- The database/table list page will only disappear when the mouse clicks on another area.
- The database switch will only be triggered by a mouse click.
It looks good to me and the user experience is improved.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Why are the changes needed?
Close #3371.
Brief change log
Modified interaction from hover to click.
How was this patch tested?
[x] Added test cases to check the loading performance and interaction method.
[x] Conducted manual tests and included screenshots to demonstrate the changes.
[x] Ran tests locally before making this pull request.
Documentation
Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)