You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 8650ed1
Browse filesBrowse the repository at this point in the historyBrowse files
fix(ui): render a message for password errors the UI does not map
We pushed a new password error from the backend with the intention that
it would be passed through to our SDKs. However, password fields have
special behavior that override the generic error builder and do not
fallback to the apierror from the backend.
Two layers to the fix:
1. Specific: handle `form_password_matches_identifier`, and add the
`unstable__errors.form_password_matches_identifier` key with an en-US
string mirroring the server copy.
2. General: filter to codes present in `mapComplexityErrors` and, when none
remain, fall back to `longMessage || message`. This restores the
passthrough for any future unrecognized code, and stops an unmapped code
arriving alongside a mapped one from contributing a blank list item.
Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
Display a proper message when a password is rejected for matching one of the account's identifiers. Previously this error rendered as the incomplete sentence "Your password must contain ." on sign-up, reset password, and the user profile password form. The new message is available under the `unstable__errors.form_password_matches_identifier` localization key, and any password error the UI does not recognize now falls back to the message returned by the API instead of an empty sentence.
0 commit comments