S16.3: Sign-up, sign-in, and sign-out

Open
  • Is something wrong?
#187 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
react, supabase, typescript
Domain
authentication, frontend

Research direction

Start with frontend/features/auth/actions.ts and frontend/features/auth/credentials-form.tsx, then read the linked S16.1 and S9.1 issues for the selected auth methods and dependencies. The forms and validation exist, but the real Supabase Auth client, account/session UI, reload persistence, protected pages, and smoke test remain. Done when the acceptance criteria work in the web app, including keeping only the public key in the browser bundle.

Written by the indexing model from the issue text.

Description

area: web blocked priority: P1 story

Roadmap story S16.3 · Project · Roadmap

Parent epic: E16 #108

Dependencies: S16.1 #186, S9.1 #148

Priority: P1 · Size: M · Sprint: 4 · Milestone: M4 · Area: web · Depends on: S16.1, S9.1 · Reqs: FR-U1 · Status: In progress

Story: As a user, I want to create an account and sign in, so that my experiments are waiting for me next time.

Acceptance criteria

  • Sign-up, sign-in, sign-out, and password reset (or magic links) work in the web app through Supabase Auth, with the methods chosen in S16.1.
  • The page header shows whether you're signed in, and pages that need an account send you to sign in.
  • The session survives a page reload. Only the public key is in the browser bundle.

Tasks

  • Build sign-in/sign-up forms with client/server validation and an explicit unavailable state
  • Add the Supabase Auth client and real sign-in, sign-up, sign-out, and recovery actions
  • Add account/session UI and persistence across reloads
  • Protect pages that need an account
  • Add a smoke test for the sign-in flow

Progress evidence (2026-11-08): Sign-in/sign-up forms and validation are committed. Their server actions explicitly return unavailable; no account is created, no session exists, and no Supabase Auth client is wired in. Evidence: PR #51, frontend/features/auth/actions.ts, frontend/features/auth/credentials-form.tsx.

Audited against committed main at 0c32c57. Local, staged, and untracked work is excluded.

Dominant language
Python
Stars
0
Forks
0
Avg merge
3h 33m
Merged PRs (30d)
50

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nfiasco/Quant-Time-Machine

All issues in nfiasco/Quant-Time-Machine

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.