25 lines
750 B
Markdown
25 lines
750 B
Markdown
# Maintainability Review - Pick'n'Play
|
|
|
|
## A) Current focus
|
|
|
|
This document tracks only active work. Completed work is intentionally omitted and can be reviewed in git history.
|
|
|
|
Active maintainability risks (priority order):
|
|
|
|
- None at the moment.
|
|
|
|
## B) Active task list
|
|
|
|
- None.
|
|
|
|
## C) Suggested execution order
|
|
|
|
1. Add new items when fresh risks are identified.
|
|
|
|
## D) Guardrails
|
|
|
|
- Keep endpoint handlers transport-focused and move business rules into services/validators.
|
|
- Keep reads side-effect free and isolate all persistence changes to explicit command paths.
|
|
- Maintain one source of truth per validation rule (backend authoritative, frontend UX hints only).
|
|
- Prefer typed DTOs over anonymous response shapes for non-trivial API payloads.
|