Account page: Username, email and join date, an export, and deletion by password #383

New issue

Closed

opened 2026-10-11 16:27:13 +00:00 by root · 13 comments

root commented

2026-10-11 16:27:13 +00:00

(Migrated from gitlab.core-project.space)

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

Parent

#364

What to build

A signed-in Player opens /account from the site navigation and sees their Username, email and join date. They can download a JSON file of their Account, their Sessions (created, last used, expires, user agent; no hash) and their Games (id, timestamps, Color, winner, ending, opponent name, UCI line and PGN from the engine). They can delete their Account after confirming with their password. Deletion cascades to their Sessions and reset tokens, clears both cookies and resets the Query cache. Their side of each Game is left with no owner, so the Game stays in the opponent's "My games".

Seam: the RPC wire; the front views

Acceptance criteria

account.export answers the document above, with no token hash, email of another Player or account id of an opponent
account.delete with the wrong password is WRONG_PASSWORD and deletes nothing; with the right one it deletes the Account, its Sessions and its reset tokens, and clears both cookies
After a deletion, the opponent's game.list still lists their shared Game, with the deleted side having no owner
The account view, its export download and its delete confirmation (including a wrong password) are tested beside the view; the navigation links to it when signed in
Every new string is in the catalogue in English and French

> _Imported from GitHub [amaurycoudr/chess-project#383](https://github.com/amaurycoudr/chess-project/issues/383), opened by [@amaurycoudr](https://github.com/amaurycoudr) on 2026-10-11 16:27 UTC._  --- ## Parent #364 ## What to build A signed-in **Player** opens `/account` from the site navigation and sees their **Username**, email and join date. They can download a JSON file of their **Account**, their **Sessions** (created, last used, expires, user agent; no hash) and their **Games** (id, timestamps, **Color**, winner, ending, opponent name, **UCI** line and PGN from the engine). They can delete their **Account** after confirming with their password. Deletion cascades to their **Sessions** and reset tokens, clears both cookies and resets the Query cache. Their side of each **Game** is left with no owner, so the **Game** stays in the opponent's "My games". Seam: the RPC wire; the front views ## Acceptance criteria - [ ] `account.export` answers the document above, with no token hash, email of another **Player** or account id of an opponent - [ ] `account.delete` with the wrong password is `WRONG_PASSWORD` and deletes nothing; with the right one it deletes the **Account**, its **Sessions** and its reset tokens, and clears both cookies - [ ] After a deletion, the opponent's `game.list` still lists their shared **Game**, with the deleted side having no owner - [ ] The account view, its export download and its delete confirmation (including a wrong password) are tested beside the view; the navigation links to it when signed in - [ ] Every new string is in the catalogue in English and French

root commented

2026-10-11 16:27:13 +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: #382, #379
Blocking: #385

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

root commented

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

(Migrated from gitlab.core-project.space)

mentioned in issue #385