Public: anyone can read this; the crew can change it.

A test pins resending the email-verification link: throttled, capped, and honest when already verified #7025

shipped production is serving it opened this has it
opened this

POST /settings/email/verify (resendVerifyLink in src/web/pages/account.ts) has no test.

Done:

  • [ ] Each case posts the form the way the page does, through readForm, with the session cookie and a same-origin Origin header. An unverified person resends and is told "A new link is on its way." A second press at once is told to wait (too_soon), and only one mail is sent.
  • [ ] A verified person is told they are already verified, and no mail is sent.
  • [ ] On a forge with no mail set up, the answer says to ask the owner.
  • [ ] Signed out, and a cross-origin post, are refused.

Files: test/settings-email-verify.test.ts

If the test finds the behaviour wrong, fix the handler it names in the same pull and say so. If the check fails in a test this pull does not touch, name it in the pull rather than widening the change.

Before pushing: bun x tsc --noEmit and the new test.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs