[#1150] fix(UI): Fix details comment error and improve components check #1334
Conversation
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
…ck (#1330) ### What changes were proposed in this pull request? The error occurred due to the failure to locate the correct variable object and its properties. Resolve: use an empty string as a substitute. Extra: 1. Initialize and reset the tree list when the metalake page is loaded. 2. Improve rendering of components check. ### Why are the changes needed? Fix: #1150 ### Does this PR introduce _any_ user-facing change? N/A ### How was this patch tested? N/A
Code Coverage Report
|
jerryshao
approved these changes
Jan 4, 2024
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.
What changes were proposed in this pull request?
The error occurred due to the failure to locate the correct variable object and its properties.
Resolve: use an empty string as a substitute.
Extra:
Why are the changes needed?
Fix: #1150
Does this PR introduce any user-facing change?
N/A
How was this patch tested?
N/A