feat(backend): document 403 response for GET /api/tasks/{id}#198
Merged
Conversation
…d} (Epta-Node#161) The ownership check (walletpublickey header required, must match task owner) was already implemented in the route handler. This commit adds the missing HTTP 403 response to the JSDoc annotation so the generated OpenAPI spec accurately documents the auth behaviour for consumers. Closes Epta-Node#161
|
@DevSolex is attempting to deploy a commit to the Jaja's projects Team on Vercel. A member of the Team first needs to authorize it. |
devJaja
self-requested a review
July 24, 2026 11:57
9 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The ownership check for
GET /api/tasks/:idandDELETE /api/tasks/:idwas already implemented in the route handlers (thewalletpublickeyheader is required and must match the task owner, returning HTTP 403 otherwise). This PR adds the missing403response entry to the OpenAPI JSDoc annotation forGET /api/tasks/{id}so the generated spec accurately documents the auth behaviour for API consumers.Closes #161
What changed
backend/src/api/routes/tasks.ts— added403response block to theGET /api/tasks/{id}JSDoc:Tests
All 34 tasks tests pass (the 8 pre-existing WebSocket stream failures in
tests/e2e/stream.test.tsare unrelated to this PR and exist onmainbefore this change):Auth coverage in
tests/tasks.test.ts: