fix: inform users of password requirements in register/change forms - #4576
Conversation
Backend now requires 10+ chars with upper/lower/digit/special on password creation/change (not login). Added a hint under each new-password field (signup, forgot-password reset, account settings) so users see the requirement before submitting instead of hitting a rejection. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (3)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. WalkthroughThe account and authentication forms now show password requirements. The account form also explains that an empty new-password field keeps the current password. The related API message is registered for translation. ChangesPassword guidance
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~5 minutes Change: Feature Merge Risk: ⚪ Minimal · up to The change adds password guidance without an identified impact on authentication workflows. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. A rabbit reads the password line Comment |
Summary
Test plan
npm run lint:no-fixclean (0 errors)npm run buildsucceeds🤖 Generated with Claude Code
Summary by CodeRabbit