Skip to content

Verification code: no space in the email, and the field accepts a pasted code with spaces - #1077

Merged
helpcodeai merged 1 commit into
mainfrom
fix/verification-code-copy
Oct 13, 2026
Merged

helpcodeai merged 1 commit into
mainfrom
fix/verification-code-copy

Conversation

@helpcodeai

Copy link
Copy Markdown
Contributor

Problem. Copying the verification code from the email didn't work.

  • The email showed the code as 504 452 with a real space between the halves, so the space was copied too.
  • The code field on /login had maxLength={6}. The browser truncates a paste to that length before onChange strips non-digits, so 504 452 arrived as 504 45: five digits, and the Verify button stayed disabled.

Fix:

  • verificationEmail shows the code exactly as typed (504452). The box's letter-spacing:10px still spaces the digits out visually, with no character in between.
  • The field has no maxLength; onChange keeps the digits of whatever is pasted, then the first six. Codes from emails already sent (with the space) work too, and so do spaces or dashes typed by hand.

Tests: email.service.spec.ts now asserts >123456< and that the spaced form is absent (9/9 pass). Frontend tsc is clean. The one eslint warning in the file (unused trialErr, line 381) is pre-existing.

…ted code with spaces

The email showed the code as "504 452" with a real space, which was copied
along with the digits. The code field had maxLength={6}, so the browser cut
the 7-character paste to "504 45" before the digits were extracted and the
code could not be submitted. The email now shows the code as typed (the
box's letter-spacing still spaces it out), and the field keeps the first six
digits of whatever is pasted, so codes from emails already sent work too.
@helpcodeai
helpcodeai merged commit 23ce41a into main Oct 13, 2026
14 checks passed
@helpcodeai
helpcodeai deleted the fix/verification-code-copy branch October 13, 2026 14:48
@github-actions github-actions Bot locked and limited conversation to collaborators Oct 13, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant