83b5072011
All checks were successful
build-and-release / build (push) Successful in 2m14s
The backend emails a plain 6-digit reset code (crates/email/templates/
password-reset.html just renders {{reset_code}}, no link) and expects
POST /api/auth/reset-password with {code, new_password}. This page was
built for a different, unused link-based flow instead: it only read a
`token` from the URL query string and posted it as `token`, a field
name the backend's ResetPasswordPayload doesn't even have. Users had
no way to type the code in at all, so submitting a request just left
them stuck back on the request screen.
Now: requesting a reset code moves straight to a "set new password"
step with a 6-digit code input, and the code is submitted under the
correct `code` field name.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
||
|---|---|---|
| .. | ||
| admin | ||
| dashboard | ||
| help-center | ||
| professionals | ||
| roles | ||
| signup | ||
| [...404].tsx | ||
| about.tsx | ||
| contact.tsx | ||
| dashboard.tsx | ||
| forgot-password.tsx | ||
| index.tsx | ||
| login.tsx | ||
| privacy.tsx | ||
| terms.tsx | ||