feat(error-handling): add global 404 JSON response filter#56
Merged
Uyoxy merged 2 commits intostellarspend:mainfrom Mar 5, 2026
Merged
feat(error-handling): add global 404 JSON response filter#56Uyoxy merged 2 commits intostellarspend:mainfrom
Uyoxy merged 2 commits intostellarspend:mainfrom
Conversation
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
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
Adds a global NestJS NotFound filter to return a consistent JSON response for unmatched routes.
Changes
Implemented NotFoundFilter
Registered filter in main.ts
Returns { statusCode: 404, message: "Route not found" }
Added test to verify behavior
Acceptance Criteria
Unknown routes return 404 with correct JSON structure
Existing routes continue to function normally
Tests pass successfully
How To Test
Start backend
Send GET /some/nonexistent/route
Expect 404 with { statusCode: 404, message: "Route not found" }