Add HTTP status code response helpers #33
Merged
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.
This PR adds convenient response helper methods to simplify common HTTP status code responses, addressing the boilerplate of manually setting
res.statusCode = 400and similar patterns.Added Response Helpers
The following methods are now available on the response object:
res.badRequest(message?)- Sets 400 Bad Requestres.unauthorized(message?)- Sets 401 Unauthorizedres.forbidden(message?)- Sets 403 Forbiddenres.notFound(message?)- Sets 404 Not Foundres.internalServerError(message?)- Sets 500 Internal Server ErrorUsage
Each helper can be used with or without an error message:
Implementation Details
Content-Type: application/jsonand sends{"error": "message"}res.end()to complete the responseTesting
Comprehensive tests validate all helpers work correctly with and without messages, ensuring proper status codes, content types, and response bodies.
Fixes #31.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.