[#1350] fix(UI): Fix fields validation when create a catalog in the web UI #1387
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
…eb UI (#1375) ### What changes were proposed in this pull request? Fix fields validation when create a catalog in the web UI. Currently, after clicking submit, it will verify correctly based on the `provider` and specific `properties`. ### Why are the changes needed? Fix: #1350 ### Does this PR introduce _any_ user-facing change? N/A ### How was this patch tested? N/A
jerryshao
added
cherry-pick
need backport
Code Coverage Report
|
qqqttt123
deleted the
cherry-pick-branch-0.3-ec5f799d883d186f3598962273ffa639855baa11
branch
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?
Fix fields validation when create a catalog in the web UI.
Currently, after clicking submit, it will verify correctly based on the
providerand specificproperties.Why are the changes needed?
Fix: #1350
Does this PR introduce any user-facing change?
N/A
How was this patch tested?
N/A