spikerj/spikersoft-issues
1
0
Fork 0
Code Issues 196 Pull Requests Actions Packages Projects Releases Wiki Activity

[Bug] Basic Info step: availability error banner persists after the error is corrected #255

New Issue
Closed
opened 2026-06-25 16:17:06 +00:00 by spikerj · 1 comment
spikerj commented 2026-06-25 16:17:06 +00:00
Owner
Copy Link
Copy Source

Severity

Medium — confuses users into thinking they still have an unresolved problem after they have already fixed it.

Area

Registration stepper — Basic Info step ("Join SpikerSoft" flow), username/email availability checking.

Bug

The Basic Info step shows an errorMessage banner when a username/email availability check fails (e.g. registration.errors.usernameCheckFailed / emailCheckFailed). The errorMessage signal is set on failure but is never cleared. Once the banner appears it stays on screen even after the user changes the input and a subsequent check succeeds, so the user is led to believe the issue is unresolved when in fact it has been corrected.

Steps to reproduce

  1. Open the "Join SpikerSoft" registration flow.
  2. Cause an availability check to fail (e.g. transient backend error / offline blip while typing a username or email).
  3. The error banner appears.
  4. Correct the input so the next check succeeds.
  5. Observe the error banner is still displayed.

Expected

The error banner should be cleared as soon as a new availability check starts (and on success), so a corrected error no longer shows a stale message.

Pointers

  • spikersoft-angular/projects/spikersoft/src/app/_components/registration-stepper/basic-info-step.ts — errorMessage signal is set in the username/email valueChanges effects but never reset.
  • spikersoft-angular/projects/spikersoft/src/app/_components/registration-stepper/basic-info-step.html — @if (errorMessage()) error banner.
## Severity Medium — confuses users into thinking they still have an unresolved problem after they have already fixed it. ## Area Registration stepper — Basic Info step ("Join SpikerSoft" flow), username/email availability checking. ## Bug The Basic Info step shows an `errorMessage` banner when a username/email availability check fails (e.g. `registration.errors.usernameCheckFailed` / `emailCheckFailed`). The `errorMessage` signal is set on failure but is **never cleared**. Once the banner appears it stays on screen even after the user changes the input and a subsequent check succeeds, so the user is led to believe the issue is unresolved when in fact it has been corrected. ### Steps to reproduce 1. Open the "Join SpikerSoft" registration flow. 2. Cause an availability check to fail (e.g. transient backend error / offline blip while typing a username or email). 3. The error banner appears. 4. Correct the input so the next check succeeds. 5. Observe the error banner is still displayed. ### Expected The error banner should be cleared as soon as a new availability check starts (and on success), so a corrected error no longer shows a stale message. ## Pointers - `spikersoft-angular/projects/spikersoft/src/app/_components/registration-stepper/basic-info-step.ts` — `errorMessage` signal is set in the username/email `valueChanges` effects but never reset. - `spikersoft-angular/projects/spikersoft/src/app/_components/registration-stepper/basic-info-step.html` — `@if (errorMessage())` error banner.
spikerj added the bug label 2026-06-25 16:17:06 +00:00
spikerj commented 2026-06-26 15:08:28 +00:00
Author
Owner
Copy Link
Copy Source

Resolved in spikersoft-angular PR #76 (merged to master). The Basic Info step now clears the availability error banner (errorMessage) as soon as the user edits the username or email field, so a corrected value no longer shows a stale error. Closing.

Resolved in spikersoft-angular PR #76 (merged to `master`). The Basic Info step now clears the availability error banner (`errorMessage`) as soon as the user edits the username or email field, so a corrected value no longer shows a stale error. Closing.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
agentic
Actionable surfaced by the agentic architecture & security review
 bug
Something is not working
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 question
More information is needed
 sonarqube
Code quality issue surfaced by SonarQube (bug / code smell)
 wontfix
This won't be fixed
No labels bug
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
spikerj (Joseph Spiker)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: spikerj/spikersoft-issues#255