Closed kellyel closed 2 months ago
Visit the preview URL for this PR (updated for commit c9b3a4a):
https://roar-staging--pr686-enh-change-password-ihfu80vd.web.app
(expires Wed, 10 Jul 2024 16:37:19 GMT)
🔥 via Firebase Hosting GitHub Action 🌎
Sign: 2631e9c58fd0104ecbfddd72a62245ddac467460
0 | 20 | 0 | 0 | 0 |
Details:
Tests for PR 686 "Change Password" from commit "c9b3a4a6d49da939aef2281ee6ebfaad... | |||
Project: roar-dashboard-e2e | Commit: c9b3a4a6d4 |
||
Status: Passed | Duration: 02:10 💡 | ||
Started: Jul 3, 2024 4:37 PM | Ended: Jul 3, 2024 4:39 PM |
I'm thinking that the change password input boxes should only show up if the user clicks on a "Change password" button. And then that could render the "New password" and "Confirm password" boxes and a separate "Update password" button that would be separate from the rest of the form.
Take a look at how GitHub handles password updating for what I'm thinking here. Mostly I'm worries about accidental input, either from the admin user or from an admin user's password manager. What do you think?
I agree. I was thinking about a way to separate this functionality out without being too intrusive to the user experience. Something like this may be a good solution. Thanks for the feedback!
Proposed changes
Adds a section on the edit users modal to allow for changing a user's password.
Types of changes
What types of changes does this pull request introduce?
Checklist
Justification of missing checklist items
Further comments