Skip to content

Registration and login forms don't show server-side validation errors per field #1988

Closed

Description

@yusuftomilola

Problem

The shared AuthForm posts email and password and shows a single error string. The backend uses forbidNonWhitelisted validation and returns field messages (for example "password must be longer than or equal to 8 characters"), plus 409 for an existing email, but the form doesn't map them to the right inputs or announce them to assistive tech.

Proposed change

Parse the error body into { field: message }, show messages under each input with aria-describedby and aria-invalid, focus the first invalid field, and handle 409 and 429 with specific copy ("email already registered", "too many attempts, try again in N seconds").

Acceptance criteria

  • Component tests cover a 400 with field errors, a 409 and a 429.

Activity

  1. sommydregent commented on Oct 17, 2026

    @sommydregent

    @sommydregent has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Hi maintainer please i will love to work on this issue.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @sommydregent to this issue.

  2. laxjovial commented on Oct 17, 2026

    @laxjovial

    @laxjovial has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Hello maintainer, i would like to work on this issue

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @laxjovial to this issue.

  3. akargi commented on Oct 17, 2026

    @akargi
    Contributor

    @akargi has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Hi Maintainer,

    I’m a full-stack developer, and I’d like to contribute to the task. I’ll implement it carefully and efficiently thoroughly understand requirements and edge cases
    Communicate promptly about suggestions or improvements. And I will provide regular progress updates and address blockers
    Align with project goals through feedback and clarification.

    Thank you,

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @akargi to this issue.

  4. drips-wave commented on Oct 17, 2026

    @drips-wave

    Congratulations, @akargi! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.

    🧑‍💻 @akargi: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

    Warning

    When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

    🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

    🌊 Happy Wave 🌊

  5. grantfox-oss commented on Oct 18, 2026

    @grantfox-oss

    🎉 This issue has been marked as completed on GrantFox!

    @akargi's PR #2052 was approved and merged by @yusuftomilola.

    🏆 @akargi: You earned 40 FoxPoints for this contribution! Your current tier: Builder (2,148 total points). Track your full progress on GrantFox.

    👏 Great work, @akargi! Keep contributing to DistinctCodes.

  6. drips-wave commented on Oct 18, 2026

    @drips-wave

    This issue has been completed by @akargi as part of the Stellar Wave Program's 10th Wave 🥳

    😎 @akargi: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

    🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions