-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Set password #3190
Set password #3190
Conversation
CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅ |
I have read the CLA Document and I hereby sign the CLA |
Hey I've made a draft PR here so we can discuss the UX better. |
Mind sharing a quick screen capture of where we're at with this? |
Expensify.cash.mp4 |
Expensify.cash.mp4I have made it so the match error only appears after the user has onblurred once on the confirm box with some input in there. The error will disappear and appear based on the passwords matching after that. The hint text of the enter a password box now turns green once the password requirements are met. |
sorry @sketchydroide I didn't mean to make this a full PR |
no worries let me know when it's ready |
sorry @shawnborton I missed your emoji reaction. I was waiting on feedback :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work! These changes are looking good, just a few comments about better variable names and styling
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! Naming nomenclature and styling is looking much better - just a few more comments
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes look good, just looks like this needs some QA steps and this is good to go
✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release. |
🚀 Deployed to staging in version: 1.0.68-5🚀
|
🚀 Deployed to production in version: 1.0.73-3🚀
|
Details
Create a new UX around setting a password during account signup.
Giving feedback to the user before submission on:
password complexity requirements
passwords matching
Fixed Issues
Fixes #1517
QA Steps
To get to this page:
trigger password reset
make sure you're logged out
navigate to here: http://localhost:8080/setpassword/[USERID]/[RESETCODE]
make sure you have credentials.login key set to your email address in local storage
Then follow the video:
https://user-images.githubusercontent.com/47184118/120825774-a23f1c80-c551-11eb-9614-a5cf2f00414e.mp4
Testing the form
Try to break the form by different combinations e.g. put in an invalid password, then replicate that in the next box. Then make the first password valid and see if the red hint turns green. And see if the passwords match error disappears.
Testing submission:
When pressing the Set Password button:
If you use an invalid password or they don't match the set password button shouldn't do anything.
If you use an expired code the Validated code is likely expired error should shot.
If you used a password that meets the complexity then you should be logged into the app and your password will have been set/changed
Tested On
Screenshots
Web
Mobile Web
Desktop
iOS
Android