[#1428] improvement(UI): Filtering empty keys when create or update #1430
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
…1412) ### What changes were proposed in this pull request? Filtering empty keys when operating create or update. <img width="480" alt="image" src="https://github.com/datastrato/gravitino/assets/17310559/c2bbf850-dfe9-4419-9f6d-6d9cd2fbe0f1"> After adding an empty key, the API will prompt an error message, so we need to prevent this from happening at the frontend level. ### Why are the changes needed? Fix: #1428 ### 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
|
mchades
approved these changes
Jan 10, 2024
qqqttt123
deleted the
cherry-pick-branch-0.3-fbd19c86e8864d1bfe3ac8eab26fa6bd15a93a61
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?
Filtering empty keys when operating create or update.
After adding an empty key, the API will prompt an error message, so we need to prevent this from happening at the frontend level.
Why are the changes needed?
Fix: #1428
Does this PR introduce any user-facing change?
N/A
How was this patch tested?
N/A