-
Notifications
You must be signed in to change notification settings - Fork 523
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
Input Values Not Resetting in Delete Dialogs #2521
Comments
Hi, once the labeling is done, could you please assign this issue to me? I would like to work on it. |
This probably happens in all dialogs, can you fix it everywhere? |
Awarding Vardhaman619: 150 points 🕹️ Well done! Check out your new contribution on oss.gg/Vardhaman619 |
/assign |
Assigned to @Vardhaman619! Please open a draft PR linking this issue within 48h |
/assign |
This issue is already assigned to another person. Please find more issues here. |
Preliminary Checks
I have reviewed the documentation: https://unkey.com/docs
I have searched for existing issues: https://github.com/unkeyed/unkey/issues
This issue is not a question, general help request, or anything other than a bug report directly related to Unkey. Please ask questions in our Discord community: https://unkey.com/discord.
Reproduction / Replay Link (Optional)
No response
Issue Summary
The form field values in the delete dialogs for roles and permissions do not reset after the dialogs are closed and reopened. This can lead to user confusion, as previously entered values remain in the fields.
Steps to Reproduce
dashboard
.Authorization > Roles > Role > Delete Role
.Expected behavior
The input fields in the delete dialogs should reset to their default state (empty) each time the dialog is closed and reopened.
Other information
This issue affects the user experience and could lead to accidental deletions if users are not aware that the input field retains previous values.
Screenshots
delete-dialog-form-field-value-not-reset-after-reopen.webm
Version info
The text was updated successfully, but these errors were encountered: