implemented the branch module establishing relationship - #365
Merged
Conversation
|
@Kaylahray is attempting to deploy a commit to the naijabuz's projects Team on Vercel. A member of the Team first needs to authorize it. |
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.
Branches, Departments, and Company Modules with Asset Integration. closes #339
Key Features Implemented
Branches Module
Handles company physical locations with CRUD APIs, including name, location, and linked company ID.
Departments Module
Represents business units within companies and branches, fully relational with Department CRUD endpoints.
Company Module
Supports companies with basic information and relations to branches and departments.
Asset Entity Update
Enhanced the existing asset entity to optionally relate to branches, aligning asset management with company locations.
All modules include strong entity definitions using TypeORM with relations.
Input validation with DTOs using
class-validator.Services encapsulate business logic for CRUD operations.
RESTful controllers expose the APIs to interact with these modules.
The project follows NestJS best practices for modular architecture and maintainability.