feature/fix bugs on organization use-cases

[CarlosP26]

🚀 Volunchain Pull Request

Mark with an x all the checkboxes that apply (like [x])

[ ] Closes #

[x] Added tests (if necessary)

[x] Run tests

[x] Run formatting

[x] Evidence attached

[x] Commented the code

📌 Type of Change

[ ] Documentation (updates to README, docs, or comments)

[x] Bug fix (non-breaking change which fixes an issue)

[x] Enhancement (non-breaking change which adds functionality)

[ ] Breaking change (fix or feature that would cause existing functionality to change)

📝 Changes description

Implemented and validated the full CRUD (Create, Read, Update, Delete) use cases for the Organization module.

This pull request finalizes the Organization module, ensuring all use cases are properly wired, validated, and tested across the stack.

The key changes include:

Finalized Use Cases: All existing use cases (create-organization.usecase.ts, delete-organization.usecase.ts, get-all-organizations.usecase.ts, get-organization-by-id.usecase.ts, update-organization.usecase.ts) have been reviewed, completed, and now expose a clear execute(input) method with explicit error handling.

Input Validation: DTOs (create-organization.dto.ts, update-organization.dto.ts) are now fully integrated with class-validator and class-transformer to provide robust input validation. Validation errors are mapped to a consistent 400 Bad Request response with a structured payload.

Controller and Routing: The organization.controller.ts has been updated to correctly invoke the finalized use cases. All endpoints are wired in src/routes/OrganizationRoutes.ts, with appropriate HTTP status codes for each operation (201 for POST, 200 for GET/PUT, 204 for DELETE).

Repository Alignment: The repository implementation has been verified to align with the organization-repository.interface.ts contract, ensuring all use cases are supported.

Comprehensive Testing: New unit tests have been added for each use case to cover both happy paths and failure modes. Integration tests have also been updated to validate the HTTP layer, with the goal of achieving at least 80% code coverage for the module.

⏰ Time spent breakdown

• Reviewing and finalizing use cases: 2 hours

• Implementing DTO validation and error mapping: 2 hours

• Updating controller and wiring routes: 1 hour

• Writing and running tests (unit & integration): 2.5 hours

• Code review and final polishing: 0.5 hours

Total time: 8 hours

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore or @coderabbit ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.