The account/ layer: one Account controller for account.me, account.export and account.delete #427

New issue

Closed

opened 2026-10-15 14:45:39 +00:00 by root · 6 comments

root commented

2026-10-15 14:45:39 +00:00

(Migrated from gitlab.core-project.space)

Parent

#421

What to build

Every account.* procedure answers from one Account controller, in a composition layer the lint allows.

A new account/ folder, right of games in the layer order.
It holds a static module and an Account controller implementing account.me, account.export and account.delete, injecting the Auth and Games services.
The Games and Auth controllers lose these procedures.
A service is added only if a procedure composes more than one call per feature.
The Account's lifecycle and persistence stay in auth. guest.claim and guest.get stay where they are.

Signed-in and signed-out Players see the same responses as before.

Seam: S1, the wire; S3, the lint.

Acceptance criteria

The lint's layer order includes account between games and devtools. Its module and controller files may import Nest, and the lint test covers both directions.
account.me, account.export and account.delete are implemented only in the Account controller.
Their integration tests, signed in and signed out, pass unchanged in what they assert.

## Parent #421 ## What to build Every `account.*` procedure answers from one Account controller, in a composition layer the lint allows. - A new `account/` folder, right of games in the layer order. - It holds a static module and an Account controller implementing `account.me`, `account.export` and `account.delete`, injecting the Auth and Games services. - The Games and Auth controllers lose these procedures. - A service is added only if a procedure composes more than one call per feature. - The Account's lifecycle and persistence stay in auth. `guest.claim` and `guest.get` stay where they are. Signed-in and signed-out Players see the same responses as before. Seam: S1, the wire; S3, the lint. ## Acceptance criteria - [ ] The lint's layer order includes `account` between games and devtools. Its module and controller files may import Nest, and the lint test covers both directions. - [ ] `account.me`, `account.export` and `account.delete` are implemented only in the Account controller. - [ ] Their integration tests, signed in and signed out, pass unchanged in what they assert.

root commented

2026-10-15 14:46:09 +00:00

(Migrated from gitlab.core-project.space)

marked this issue as related to #421