Skip to content
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

Fix | Show correct error page on password incorrect #3055

Merged
merged 1 commit into from
Feb 5, 2025

Conversation

coldlink
Copy link
Member

@coldlink coldlink commented Feb 5, 2025

What does this change?

When using the password option instead of passcodes, this occurs on the /signin/password page now.

However we made a mistake in the error handling ternary operator to determine the error page.

We've fixed it so that usePasscode is falsy, then go to /signin/password as the error page, as the user is using password to sign in.

Tested

  • DEV
  • CODE

@coldlink coldlink added the passwordless PRs/Issues related to passwordless/passcode functionality label Feb 5, 2025
@coldlink coldlink changed the title fix(passcodes): show corrent error page on password incorrect Fix | Show correct error page on password incorrect Feb 5, 2025
@coldlink coldlink marked this pull request as ready for review February 5, 2025 14:36
@coldlink coldlink requested a review from a team as a code owner February 5, 2025 14:36
Copy link
Contributor

@pvighi pvighi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good job adding a test case for this as well

@coldlink coldlink enabled auto-merge February 5, 2025 14:47
@coldlink coldlink merged commit 93ba9a5 into main Feb 5, 2025
21 checks passed
@coldlink coldlink deleted the mm/fix-passcode-password-flow branch February 5, 2025 14:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
passwordless PRs/Issues related to passwordless/passcode functionality
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants