Added response interceptor and swagger clean up #114
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.
📌 Pull Request Title
Description
le(s):
The Response interceptor and swaager clean up has been achieved according to the below instructions and all criterias were met.
Standardized API responses using NestJS interceptors. Clean up Swagger decorators and DTOs across all modules to improved documentation and expected request/response clarity.
Proposed Actions:
Interceptor
Created a global ResponseInterceptor that wraps all successful responses in a common format:
{
"status": "success",
"data": {},
"message": "optional"
}
Swagger Cleanup
Reviewed and correct @ApiProperty() decorators in all DTOs across modules.
Ensured required fields, types, and descriptions are properly annotated.
Setup
Added interceptor globally in main.ts.
Testing:
Verified consistent response formats across all endpoints.
Run Swagger UI and confirm accurate documentation.
Unit test the interceptor behavior.
Related Issues
Changes Made
How to Test
Screenshots (if applicable)
Checklist
close[Add Response Interceptors & Swagger Cleanup #89 ]