Implement Treasury API Endpoints #32
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.
close #28
Overview
Implemented RESTful API endpoints for treasury operations (e.g., create, update, fetch treasuries and transactions) with proper authentication, authorization, and event-based communication.
Changes Made
Treasury Controller :
Added endpoints for treasury and transaction management.
Used Swagger annotations for API documentation.
DTOs and Validation :
Created DTOs for requests/responses.
Added validation to ensure data integrity.
Authentication & Authorization :
Integrated JwtAuthGuard and RolesGuard for secure access.
Implemented checkUserAccessToTreasury and checkUserPermission methods.
Event-Based Communication :
Published events for treasury/transaction updates using TreasuryEvents.
Error Handling :
Handled errors like NotFoundException, ForbiddenException, and BadRequestException.
Testing Status
Unit and integration tests pending.
Manual testing not yet performed.