-
Notifications
You must be signed in to change notification settings - Fork 319
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Improvement] Filtering empty keys when create or update in the web UI #1428
Labels
improvement
Improvements on everything
Comments
jerryshao
pushed a commit
that referenced
this issue
Jan 10, 2024
…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
github-actions bot
pushed a commit
that referenced
this issue
Jan 10, 2024
…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
mchades
pushed a commit
that referenced
this issue
Jan 10, 2024
…1430) ### 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 Co-authored-by: CHEYNE <contact@ch3yne.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What would you like to be improved?
Filtering empty keys when operating create or update.
How should we improve?
Remove empty keys' properties before submitting.
The text was updated successfully, but these errors were encountered: