Enhance UX for Category Edit Dialog in Knowledge Base Section of Helpdesk Portal #1956
+13
−4
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
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.
Issue:
Passing category doc fields directly in
v-modelinputs in the category edit dialog caused immediate updates before saving. Unsaved changes would disappear upon refresh, and the dialog did not close automatically after saving.Fix:
Temporary Variables: Used temporary variables (
newCategoryName,newCategoryDescription,newCategoryIcon) to hold user input instead of binding directly tocategory.docfields. Added awatchfunction to update these variables with doc values when the dialog opens, preventing immediate UI updates before saving.Dialog Handling: Configured the dialog to close automatically after saving, reducing the number of user actions required.
Before Fix
before.webm
After Fix
after.webm