Sign-up and sign-in pages: the navigation names the Account, a refresh keeps it signed in #379

New issue

Closed

opened 2026-10-11 16:26:51 +00:00 by root · 14 comments

root commented

2026-10-11 16:26:51 +00:00

(Migrated from gitlab.core-project.space)

Imported from GitHub amaurycoudr/chess-project#379, opened by @amaurycoudr on 2026-10-11 16:26 UTC.

Parent

#364

What to build

A Player signs up at /sign-up and sees whether a Username is free while typing: the format is checked locally with the contract's schema, then availability through a debounced read. Every refusal shows its reason. They sign in at /sign-in and sign out from the site navigation. The navigation shows "Sign in" when signed out and the Username with "Sign out" when signed in. The signed-in Account is one Query entry from account.me, and signing in or out resets the whole Query cache. A shared refresh-and-retry wrapper sits on every vertical's client. On UNAUTHORIZED it refreshes once per tab at a time, then retries once. A failed refresh shows the Player signed out rather than looping. Every new string is in the Paraglide catalogue in English and French.

Seam: the front views (each beside its view with the auth vertical's harness and MSW)

Acceptance criteria

The sign-up view shows each refusal (email taken, Username taken, Username not allowed with its reason, password too short or too long) and the live Username check
The sign-in view shows one message for a wrong email or password
The site navigation is tested signed in (Username, "Sign out") and signed out ("Sign in")
One UNAUTHORIZED triggers one refresh and one retry; two calls failing together refresh once; a refresh that succeeds followed by a retry that fails shows the Player signed out
Signing in and signing out reset the Query cache
Every new string is in the catalogue in English and French
The front's new auth vertical is declared in the front lint config's per-vertical rules, and the other verticals' sibling-import rules name it (the owner ruled on the accounts breakdown that declaring a folder the spec creates counts as the requested lint change; nothing else in lint config changes)

> _Imported from GitHub [amaurycoudr/chess-project#379](https://github.com/amaurycoudr/chess-project/issues/379), opened by [@amaurycoudr](https://github.com/amaurycoudr) on 2026-10-11 16:26 UTC._  --- ## Parent #364 ## What to build A **Player** signs up at `/sign-up` and sees whether a **Username** is free while typing: the format is checked locally with the contract's schema, then availability through a debounced read. Every refusal shows its reason. They sign in at `/sign-in` and sign out from the site navigation. The navigation shows "Sign in" when signed out and the **Username** with "Sign out" when signed in. The signed-in **Account** is one Query entry from `account.me`, and signing in or out resets the whole Query cache. A shared refresh-and-retry wrapper sits on every vertical's client. On UNAUTHORIZED it refreshes once per tab at a time, then retries once. A failed refresh shows the **Player** signed out rather than looping. Every new string is in the Paraglide catalogue in English and French. Seam: the front views (each beside its view with the `auth` vertical's harness and MSW) ## Acceptance criteria - [ ] The sign-up view shows each refusal (email taken, **Username** taken, **Username** not allowed with its reason, password too short or too long) and the live **Username** check - [ ] The sign-in view shows one message for a wrong email or password - [ ] The site navigation is tested signed in (**Username**, "Sign out") and signed out ("Sign in") - [ ] One UNAUTHORIZED triggers one refresh and one retry; two calls failing together refresh once; a refresh that succeeds followed by a retry that fails shows the **Player** signed out - [ ] Signing in and signing out reset the Query cache - [ ] Every new string is in the catalogue in English and French - [ ] The front's new auth vertical is declared in the front lint config's per-vertical rules, and the other verticals' sibling-import rules name it (the owner ruled on the accounts breakdown that declaring a folder the spec creates counts as the requested lint change; nothing else in lint config changes)

root commented

2026-10-11 16:26:51 +00:00

(Migrated from gitlab.core-project.space)

GitHub issue relations, imported as "related" links (GitLab CE has no sub-issues or blocking links).

Parent (sub-issue of): #364
Blocked by: #378
Blocking: #384, #383, #380

> _GitHub issue relations, imported as "related" links (GitLab CE has no sub-issues or blocking links)._  - Parent (sub-issue of): #364 - Blocked by: #378 - Blocking: #384, #383, #380

root commented

2026-10-13 08:39:47 +00:00

(Migrated from gitlab.core-project.space)

mentioned in issue #380