Review finding 18/19 · conventional-comment suggestion · area binder · gate: follow-up
To add once it exists: label binder. (Already applied: enhancement, documentation.)
Problem
FirstClassErrors.Usage (the opted-in sample that the generated-catalog snapshot tests document) has no request-binder example. The existing StatementUploadEndpoint is the ideal primary-adapter boundary to bind.
Impact
The binder is absent from the living, generated documentation sample, so there is no end-to-end, snapshot-tested example of the feature for consumers to copy, and the generated catalog never exercises the binder path.
Direction
Add a binder-backed endpoint to Usage (for example, bind a request into StatementUploadEndpoint's command) so it appears in the snapshot-tested catalog and serves as the canonical example.
Context
Surfaced by the RequestBinder review (design spec #126, shipped in #141). Finding 18 of 19.
Problem
FirstClassErrors.Usage(the opted-in sample that the generated-catalog snapshot tests document) has no request-binder example. The existingStatementUploadEndpointis the ideal primary-adapter boundary to bind.Impact
The binder is absent from the living, generated documentation sample, so there is no end-to-end, snapshot-tested example of the feature for consumers to copy, and the generated catalog never exercises the binder path.
Direction
Add a binder-backed endpoint to
Usage(for example, bind a request intoStatementUploadEndpoint's command) so it appears in the snapshot-tested catalog and serves as the canonical example.Context
Surfaced by the RequestBinder review (design spec #126, shipped in #141). Finding 18 of 19.