The changes load when the file comes near.
Change request saved in this viewer
This review has no pull request, so the decision stays in this viewer.
An agent sees the decision only while it watches this review. If the agent is not answering in chat, ask it there: Continue the mcp-review at /demo-xxl
Move the storefront API to typed handlers
Coverage
- Presentation
- All 1051 selected changes are placed. 1050 in groups · 0 unbucketed · 1 generated · 0 without a text diff
- Explanations
- 8 of 8 groups have an explanation.
- Agent analysis
- Reading the analysis status…
- Human review
- 0 of 1051 hunks are marked reviewed.
Outdated discussions 0
These discussions have no verified location in the displayed changes. Each keeps its original code and stays open to replies and resolution.
Typed request pipeline
The pipeline is the reason for this change. A handler now declares its method, path, access and schemas, and runHandler does the rest in a fixed order.
Order of the checks
- Access: a
useroradminendpoint without a session answers 401, and a non-admin on anadminendpoint 403. - Validation: the path, the query and the body each pass their schema, or the answer is 422 with the problems.
- The handler runs. An
HttpErrorbecomes its status and code; any other error becomes a 500 that quotes the request ID.
What to check
readJsoncaps the body at 1 MiB and answers 413 above it.- A 204 answer writes no body.
app.tskeepslisten, so the deployment does not change.src/handlers/index.tsreplaces the Express route table and lists each literal path before the path with a parameter.
The changes load when the file comes near.
The changes load when the file comes near.
The changes load when the file comes near.
The changes load when the file comes near.
The changes load when the file comes near.
The changes load when the file comes near.
The changes load when the file comes near.
The changes load when the file comes near.