Rewrite the front's rules and ADR 0011 as the owner decided #414
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
spec
wayfinder:grilling
wayfinder:map
wayfinder:prototype
wayfinder:research
wayfinder:task
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
#415 Merge each route's view and UI into one page file
amaurycoudr/chess-project
Reference
amaurycoudr/chess-project#414
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Parent
#408
What to build
The front's rules say what the owner decided, and lint enforces them: one page file per route, routes may import what they configure,
lib/may hold reads several verticals share, presentationalcomponents/keep their boundary, and a TanStack Formformorfieldobject may be passed to a component. This is the dedicated rule changeCLAUDE.mdrequires; no app code changes.Seam: S1 — the front lint plugin through its test.
Acceptance criteria
CODING_STANDARDS.mdcarries the lint and review rules listed in #408's Implementation Decisions.front/view-is-compositionis deleted with its test cases.components/still reject Query, zustand, oRPC, hooks and services; page files may use them;@/lib/formis allowed incomponents/; routes may import a vertical's page files, services and exported constants..view.tsx/.ui.tsxuntil the next ticket.marked this issue as related to #408
mentioned in issue #415
marked this issue as related to #415
mentioned in commit
0818df5e7amentioned in merge request !534
mentioned in commit
a37c5c0f71