feat(j-s): Subpoena delivery and endpoint for updates #15918
Conversation
…sland.is into j-s/xrd-api-subpoena
WalkthroughThis pull request introduces enhancements to the judicial system's backend, focusing on managing subpoenas. It includes the creation of a new Changes
Possibly related PRs
Suggested labels
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
Datadog ReportAll test runs ✅ 9 Total Test Services: 0 Failed, 9 Passed Test Services
🔻 Code Coverage Decreases vs Default Branch (3) |
…subpoenas Rather than having the logic all over and confusing
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
Outside diff range and nitpick comments (1)
apps/judicial-system/backend/src/app/modules/police/police.service.ts (1)
511-578: LGTM! ThecreateSubpoenamethod is well-implemented.The method correctly extracts the necessary information from the
workingCaseanddefendantobjects to construct the API request payload. It handles the API response appropriately, returning thesubpoenaIdon success and logging errors on failure.A few minor suggestions for improvement:
- Consider adding type annotations for the
subpoenaIdvariable to improve code readability and type safety.- Consider extracting the error handling logic (logging and posting error events) into a separate method to promote code reuse and maintainability.
Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Files selected for processing (24)
- apps/judicial-system/backend/migrations/20240827132504-create-subpoena.js (1 hunks)
- apps/judicial-system/backend/src/app/app.module.ts (2 hunks)
- apps/judicial-system/backend/src/app/modules/case/case.service.ts (2 hunks)
- apps/judicial-system/backend/src/app/modules/defendant/defendant.service.ts (1 hunks)
- apps/judicial-system/backend/src/app/modules/defendant/internalDefendant.controller.ts (1 hunks)
- apps/judicial-system/backend/src/app/modules/index.ts (1 hunks)
- apps/judicial-system/backend/src/app/modules/notification/notification.service.ts (1 hunks)
- apps/judicial-system/backend/src/app/modules/police/models/createSubpoena.response.ts (1 hunks)
- apps/judicial-system/backend/src/app/modules/police/police.service.ts (2 hunks)
- apps/judicial-system/backend/src/app/modules/subpoena/dto/deliver.dto.ts (1 hunks)
- apps/judicial-system/backend/src/app/modules/subpoena/dto/updateSubpoena.dto.ts (1 hunks)
- apps/judicial-system/backend/src/app/modules/subpoena/guards/subpoena.decorator.ts (1 hunks)
- apps/judicial-system/backend/src/app/modules/subpoena/guards/subpoenaExists.guard.ts (1 hunks)
- apps/judicial-system/backend/src/app/modules/subpoena/internalSubpoena.controller.ts (1 hunks)
- apps/judicial-system/backend/src/app/modules/subpoena/models/deliver.response.ts (1 hunks)
- apps/judicial-system/backend/src/app/modules/subpoena/models/subpoena.model.ts (1 hunks)
- apps/judicial-system/backend/src/app/modules/subpoena/subpoena.module.ts (1 hunks)
- apps/judicial-system/backend/src/app/modules/subpoena/subpoena.service.ts (1 hunks)
- apps/judicial-system/xrd-api/src/app/app.controller.ts (3 hunks)
- apps/judicial-system/xrd-api/src/app/app.service.ts (3 hunks)
- apps/judicial-system/xrd-api/src/app/dto/subpoena.dto.ts (1 hunks)
- apps/judicial-system/xrd-api/src/app/models/subpoena.response.ts (1 hunks)
- libs/judicial-system/formatters/src/lib/formatters.ts (1 hunks)
- libs/judicial-system/message/src/lib/message.ts (2 hunks)
Files skipped from review due to trivial changes (2)
- apps/judicial-system/backend/src/app/modules/case/case.service.ts
- libs/judicial-system/formatters/src/lib/formatters.ts
Additional context used
Path-based instructions (22)
apps/judicial-system/backend/src/app/modules/subpoena/models/deliver.response.ts (1)
Pattern
apps/**/*: "Confirm that the code adheres to the following:
- NextJS best practices, including file structure, API routes, and static generation methods.
- Efficient state management and server-side rendering techniques.
- Optimal use of TypeScript for component and utility type safety."
apps/judicial-system/backend/src/app/modules/police/models/createSubpoena.response.ts (1)
Pattern
apps/**/*: "Confirm that the code adheres to the following:
- NextJS best practices, including file structure, API routes, and static generation methods.
- Efficient state management and server-side rendering techniques.
- Optimal use of TypeScript for component and utility type safety."
apps/judicial-system/backend/src/app/modules/subpoena/guards/subpoena.decorator.ts (1)
Pattern
apps/**/*: "Confirm that the code adheres to the following:
- NextJS best practices, including file structure, API routes, and static generation methods.
- Efficient state management and server-side rendering techniques.
- Optimal use of TypeScript for component and utility type safety."
apps/judicial-system/backend/src/app/modules/subpoena/dto/deliver.dto.ts (1)
Pattern
apps/**/*: "Confirm that the code adheres to the following:
- NextJS best practices, including file structure, API routes, and static generation methods.
- Efficient state management and server-side rendering techniques.
- Optimal use of TypeScript for component and utility type safety."
apps/judicial-system/xrd-api/src/app/models/subpoena.response.ts (1)
Pattern
apps/**/*: "Confirm that the code adheres to the following:
- NextJS best practices, including file structure, API routes, and static generation methods.
- Efficient state management and server-side rendering techniques.
- Optimal use of TypeScript for component and utility type safety."
apps/judicial-system/backend/src/app/modules/subpoena/guards/subpoenaExists.guard.ts (1)
Pattern
apps/**/*: "Confirm that the code adheres to the following:
- NextJS best practices, including file structure, API routes, and static generation methods.
- Efficient state management and server-side rendering techniques.
- Optimal use of TypeScript for component and utility type safety."
apps/judicial-system/xrd-api/src/app/dto/subpoena.dto.ts (1)
Pattern
apps/**/*: "Confirm that the code adheres to the following:
- NextJS best practices, including file structure, API routes, and static generation methods.
- Efficient state management and server-side rendering techniques.
- Optimal use of TypeScript for component and utility type safety."
apps/judicial-system/backend/src/app/modules/subpoena/subpoena.module.ts (1)
Pattern
apps/**/*: "Confirm that the code adheres to the following:
- NextJS best practices, including file structure, API routes, and static generation methods.
- Efficient state management and server-side rendering techniques.
- Optimal use of TypeScript for component and utility type safety."
apps/judicial-system/backend/src/app/modules/subpoena/dto/updateSubpoena.dto.ts (1)
Pattern
apps/**/*: "Confirm that the code adheres to the following:
- NextJS best practices, including file structure, API routes, and static generation methods.
- Efficient state management and server-side rendering techniques.
- Optimal use of TypeScript for component and utility type safety."
apps/judicial-system/backend/src/app/modules/index.ts (1)
Pattern
apps/**/*: "Confirm that the code adheres to the following:
- NextJS best practices, including file structure, API routes, and static generation methods.
- Efficient state management and server-side rendering techniques.
- Optimal use of TypeScript for component and utility type safety."
apps/judicial-system/backend/src/app/modules/subpoena/models/subpoena.model.ts (1)
Pattern
apps/**/*: "Confirm that the code adheres to the following:
- NextJS best practices, including file structure, API routes, and static generation methods.
- Efficient state management and server-side rendering techniques.
- Optimal use of TypeScript for component and utility type safety."
apps/judicial-system/backend/src/app/app.module.ts (1)
Pattern
apps/**/*: "Confirm that the code adheres to the following:
- NextJS best practices, including file structure, API routes, and static generation methods.
- Efficient state management and server-side rendering techniques.
- Optimal use of TypeScript for component and utility type safety."
apps/judicial-system/backend/migrations/20240827132504-create-subpoena.js (1)
Pattern
apps/**/*: "Confirm that the code adheres to the following:
- NextJS best practices, including file structure, API routes, and static generation methods.
- Efficient state management and server-side rendering techniques.
- Optimal use of TypeScript for component and utility type safety."
apps/judicial-system/xrd-api/src/app/app.controller.ts (1)
Pattern
apps/**/*: "Confirm that the code adheres to the following:
- NextJS best practices, including file structure, API routes, and static generation methods.
- Efficient state management and server-side rendering techniques.
- Optimal use of TypeScript for component and utility type safety."
apps/judicial-system/backend/src/app/modules/defendant/internalDefendant.controller.ts (1)
Pattern
apps/**/*: "Confirm that the code adheres to the following:
- NextJS best practices, including file structure, API routes, and static generation methods.
- Efficient state management and server-side rendering techniques.
- Optimal use of TypeScript for component and utility type safety."
apps/judicial-system/backend/src/app/modules/notification/notification.service.ts (1)
Pattern
apps/**/*: "Confirm that the code adheres to the following:
- NextJS best practices, including file structure, API routes, and static generation methods.
- Efficient state management and server-side rendering techniques.
- Optimal use of TypeScript for component and utility type safety."
apps/judicial-system/backend/src/app/modules/subpoena/internalSubpoena.controller.ts (1)
Pattern
apps/**/*: "Confirm that the code adheres to the following:
- NextJS best practices, including file structure, API routes, and static generation methods.
- Efficient state management and server-side rendering techniques.
- Optimal use of TypeScript for component and utility type safety."
libs/judicial-system/message/src/lib/message.ts (1)
Pattern
libs/**/*: "Confirm that the code adheres to the following:
- Reusability of components and hooks across different NextJS apps.
- TypeScript usage for defining props and exporting types.
- Effective tree-shaking and bundling practices."
apps/judicial-system/backend/src/app/modules/subpoena/subpoena.service.ts (1)
Pattern
apps/**/*: "Confirm that the code adheres to the following:
- NextJS best practices, including file structure, API routes, and static generation methods.
- Efficient state management and server-side rendering techniques.
- Optimal use of TypeScript for component and utility type safety."
apps/judicial-system/xrd-api/src/app/app.service.ts (1)
Pattern
apps/**/*: "Confirm that the code adheres to the following:
- NextJS best practices, including file structure, API routes, and static generation methods.
- Efficient state management and server-side rendering techniques.
- Optimal use of TypeScript for component and utility type safety."
apps/judicial-system/backend/src/app/modules/defendant/defendant.service.ts (1)
Pattern
apps/**/*: "Confirm that the code adheres to the following:
- NextJS best practices, including file structure, API routes, and static generation methods.
- Efficient state management and server-side rendering techniques.
- Optimal use of TypeScript for component and utility type safety."
apps/judicial-system/backend/src/app/modules/police/police.service.ts (1)
Pattern
apps/**/*: "Confirm that the code adheres to the following:
- NextJS best practices, including file structure, API routes, and static generation methods.
- Efficient state management and server-side rendering techniques.
- Optimal use of TypeScript for component and utility type safety."
Biome
apps/judicial-system/backend/migrations/20240827132504-create-subpoena.js
[error] 1-1: Redundant use strict directive.
The entire contents of JavaScript modules are automatically in strict mode, with no statement needed to initiate it.
Safe fix: Remove the redundant use strict directive.(lint/suspicious/noRedundantUseStrict)
Additional comments not posted (34)
apps/judicial-system/backend/src/app/modules/subpoena/models/deliver.response.ts (1)
3-6: LGTM!The
DeliverResponseclass is well-structured and follows best practices:
- The class name clearly conveys its purpose.
- The
@ApiPropertydecorator is used correctly to specify the type of thedeliveredproperty for API documentation.- The non-null assertion operator
!is used appropriately to indicate that thedeliveredproperty is always expected to be present.apps/judicial-system/backend/src/app/modules/police/models/createSubpoena.response.ts (1)
3-6: LGTM!The
CreateSubpoenaResponseclass follows the best practices for defining a response DTO:
- The class name is clear and follows the naming convention.
- The
@ApiPropertydecorator is used correctly to specify the type ofsubpoenaIdfor API documentation.- The
subpoenaIdproperty is marked as non-nullable using the!operator.The structure and syntax are correct.
apps/judicial-system/backend/src/app/modules/subpoena/guards/subpoena.decorator.ts (1)
1-7: LGTM!The custom
CurrentSubpoenadecorator is implemented correctly and follows NestJS best practices. It effectively extracts the currentSubpoenaobject from the request context, making it accessible in the route handler. The use ofcreateParamDecoratorand TypeScript ensures type safety and adherence to the framework's guidelines.The decorator enhances the management and utilization of subpoena-related data within the application, streamlining the process of accessing this information across the codebase.
apps/judicial-system/backend/src/app/modules/subpoena/dto/deliver.dto.ts (2)
7-12: LGTM!The
DeliverDtoclass is well-structured and follows the appropriate naming convention for a DTO class. It serves a clear purpose of delivering user-related data and ensures type safety by importing theUsertype from the appropriate module.
8-11: LGTM!The
userproperty in theDeliverDtoclass is well-defined with appropriate validation decorators (@IsNotEmpty()and@IsObject()) to ensure data integrity. The@ApiProperty()decorator enhances API documentation by specifying the type of the property. Thereadonlymodifier and non-null assertion operator!provide additional type safety and prevent unintended reassignment of the property.apps/judicial-system/xrd-api/src/app/models/subpoena.response.ts (2)
7-13: LGTM!The
SubpoenaResponseclass is well-defined and serves its purpose as a DTO for subpoena responses. The properties are appropriately typed and decorated for API documentation.
15-22: LGTM!The
DefenderInfoclass is well-structured and effectively encapsulates the relevant information about the defender. The use of the@IsEnumdecorator ensures data integrity for thedefenderChoiceproperty, and the@ApiPropertydecorators provide necessary metadata for API documentation.apps/judicial-system/backend/src/app/modules/subpoena/guards/subpoenaExists.guard.ts (1)
1-27: LGTM!The
SubpoenaExistsGuardclass follows NestJS best practices and provides a robust way to validate the existence of a subpoena based on thesubpoenaIdparameter in the request URL. The class correctly handles the case when thesubpoenaIdis missing by throwing aBadRequestException. Retrieving the subpoena using theSubpoenaServiceand attaching it to the request object is a good approach to make the subpoena available to subsequent handlers.The code is well-structured, and the logic is clear and concise. Great job!
apps/judicial-system/xrd-api/src/app/dto/subpoena.dto.ts (1)
7-27: LGTM!The
UpdateSubpoenaDtoclass is well-structured and follows best practices:
- The properties are correctly typed and marked as optional.
- Appropriate validation decorators are used to ensure data integrity.
@ApiPropertydecorators are used for seamless Swagger integration.- The
DefenderChoiceenum is correctly imported and used.The class provides a clean and validated way to update subpoena information.
apps/judicial-system/backend/src/app/modules/subpoena/subpoena.module.ts (1)
1-22: LGTM! TheSubpoenaModulefollows NestJS best practices and effectively encapsulates subpoena-related functionality.The module structure and design are well-organized and adhere to NestJS conventions. Key observations:
- The use of
forwardRefis appropriate to handle circular dependencies between modules.- The module properly integrates with other relevant modules such as
CaseModule,DefendantModule, andPoliceModule.- The module leverages Sequelize for ORM capabilities, defining the necessary models (
SubpoenaandDefendant).- The module registers the
InternalSubpoenaControllerandSubpoenaService, promoting a clean separation of concerns.Overall, the
SubpoenaModuleeffectively encapsulates subpoena-related functionality and sets up the necessary infrastructure for managing subpoenas within the judicial system.apps/judicial-system/backend/src/app/modules/subpoena/dto/updateSubpoena.dto.ts (1)
7-42: LGTM! TheUpdateSubpoenaDtoclass is well-structured and effectively uses decorators for validation and API documentation.The class demonstrates several positive aspects:
- Each property is declared on a separate line, enhancing readability.
- The use of
@IsOptionaldecorator for all properties allows flexibility in updating subpoena information.- The validation decorators such as
@IsBoolean,@IsString, and@IsEnumensure type safety and data integrity.- The
@ApiPropertyOptionalannotations improve API documentation by specifying the expected type and optionality of each property.- The
defenderChoiceproperty uses theDefenderChoiceenum, promoting consistency and type safety.Overall, the class provides a clear and validated structure for updating subpoena information, which enhances the robustness and maintainability of the codebase. The effective use of decorators for validation and API documentation improves the developer experience and reduces the likelihood of errors.
apps/judicial-system/backend/src/app/modules/index.ts (1)
21-21: LGTM!The export statement for the
SubpoenaModulefollows the established pattern in the file and makes the module available for use in other parts of the application. This change aligns with the PR objective of implementing subpoena-related functionality in the judicial system's backend.apps/judicial-system/backend/src/app/modules/subpoena/models/subpoena.model.ts (4)
1-15: Imports look good!The file correctly imports the necessary dependencies from
sequelize-typescript,@nestjs/swagger, and other application models. The imports are well-structured and follow the best practices.
17-20:@Tabledecorator configuration looks good!The
@Tabledecorator correctly defines thetableNameas'subpoena'and enables timestamps by settingtimestampstotrue. This configuration aligns with the best practices for defining Sequelize models.
21-66: Model properties are well-defined!The
Subpoenamodel extends the SequelizeModelclass and defines several properties with appropriate data types, validation decorators, and relationships:
- The
idproperty is correctly defined as the primary key withUUIDdata type and default value.- The
createdandmodifiedproperties use the@CreatedAtand@UpdatedAtdecorators for automatic timestamp management.- The
subpoenaId,acknowledged, andcommentproperties are optional and use appropriate data types.- The
defendantIdandcaseIdproperties are correctly defined as foreign keys using the@ForeignKeydecorator.- The
@BelongsTodecorator is used to define the relationships with theDefendantandCasemodels.- The
@ApiPropertyand@ApiPropertyOptionaldecorators are used for Swagger documentation.The property definitions align with the best practices for defining Sequelize models and follow the NestJS conventions for API documentation.
1-67: Overall structure and adherence to best practices are excellent!The
subpoena.model.tsfile is well-structured and follows the NestJS conventions and best practices for defining Sequelize models:
- The file is organized into logical sections: imports, model definition, and property definitions.
- The model class is decorated with appropriate Sequelize and NestJS decorators for database mapping and API documentation.
- The property definitions use TypeScript types for type safety and follow the best practices for defining Sequelize models.
- The file exports the model class for use in other parts of the application, promoting modularity and reusability.
The code adheres to the following:
- NestJS best practices for defining Sequelize models and integrating with the NestJS framework.
- Efficient use of Sequelize decorators and configurations for database mapping and relationships.
- Optimal use of TypeScript for model property type safety and API documentation.
Great job on structuring the
Subpoenamodel and ensuring adherence to best practices!apps/judicial-system/backend/src/app/app.module.ts (1)
33-33: LGTM!The
SubpoenaModuleis imported and added to theAppModulefollowing the existing patterns and best practices. This change expands the system's capabilities to handle subpoenas without introducing any apparent issues.Also applies to: 54-54
apps/judicial-system/backend/migrations/20240827132504-create-subpoena.js (1)
3-68: LGTM!The migration script follows best practices and correctly defines the structure of the
subpoenatable. The use of transactions ensures data integrity during the migration process.apps/judicial-system/xrd-api/src/app/app.controller.ts (1)
67-77: LGTM!The new endpoint for updating subpoenas looks good:
- The endpoint URL and HTTP method follow REST conventions.
- The use of
ParseUUIDPipeensures that thesubpoenaIdparameter is a valid UUID.- The
UpdateSubpoenaDtoandSubpoenaResponseprovide a clear contract for the request and response.- The
@ApiResponsedecorator improves the API documentation.One minor suggestion:
- Review the debug log statement to ensure it does not log any sensitive information about the subpoena or the update request.
apps/judicial-system/backend/src/app/modules/defendant/internalDefendant.controller.ts (2)
68-68: LGTM!The updated API documentation accurately reflects the new functionality of the
updateDefendantmethod to update defendant information by case and national ID.
76-76: LGTM!The updated logging statement accurately reflects the new functionality of the
updateDefendantmethod and provides useful debugging information by including the case ID.apps/judicial-system/backend/src/app/modules/notification/notification.service.ts (1)
72-79: LGTM!The code segment correctly generates a notification message of type
MessageType.DELIVERY_TO_POLICE_SUBPOENAfor each defendant associated with the case. This ensures that the police are notified about the subpoena delivery for each defendant, enhancing the comprehensiveness of the notification system.The message includes the necessary information such as the user, case ID, and defendant ID, making it suitable for its intended purpose.
apps/judicial-system/backend/src/app/modules/subpoena/internalSubpoena.controller.ts (3)
53-62: LGTM!The
getSubpoenamethod is well-implemented. It uses theSubpoenaExistsGuardto ensure the subpoena exists and the@CurrentSubpoena()decorator to retrieve it. Logging the action is a good practice for debugging.
64-74: LGTM!The
updateSubpoenamethod is well-implemented. It uses theSubpoenaExistsGuardto validate the subpoena's existence and delegates the update operation to thesubpoenaService. Logging the action is a good practice for debugging.
76-114: LGTM!The
deliverSubpoenaToPolicemethod is well-implemented. It uses multiple guards to ensure the validity of the case, defendant, and case type. Generating the PDF and encoding it in Base64 before sending it to thesubpoenaServiceis a good practice for data transfer. Error handling and logging are implemented for the PDF generation process, which is crucial for debugging.libs/judicial-system/message/src/lib/message.ts (2)
25-25: LGTM!The new message type
DELIVERY_TO_POLICE_SUBPOENAis added correctly to theMessageTypeenum. The naming convention is consistent, and the placement is appropriate.
58-58: Verify thedeliverSubpoenaToPolicefunction.The new entry in the
messageEndpointobject is added correctly, mapping theDELIVERY_TO_POLICE_SUBPOENAmessage type to thedeliverSubpoenaToPolicefunction. The mapping is consistent with the pattern used for other message types.Ensure that the
deliverSubpoenaToPolicefunction is defined in the codebase and has the expected signature. Run the following script to verify:apps/judicial-system/backend/src/app/modules/subpoena/subpoena.service.ts (4)
34-39: LGTM!The
createSubpoenamethod correctly creates a new subpoena record linked to the provided defendant.
41-89: Looks good!The
updatemethod correctly updates the subpoena and defendant records within a transaction. The error handling and logging for unexpected row counts is a nice touch.
91-106: Nicely done!The
findBySubpoenaIdmethod correctly fetches a subpoena record by its ID, with proper error handling for missing or invalid input.
108-139: Great work!The
deliverSubpoenaToPolicemethod handles the complex process of creating and delivering a subpoena to the police in a clear and error-safe manner. The logging and error handling ensure that any issues are properly tracked and communicated.apps/judicial-system/xrd-api/src/app/app.service.ts (2)
83-93: LGTM!The method is correctly using the audit trail service to audit the subpoena update action and delegating the actual update logic to the private method
updateSubpoenaInfo.
95-168: Excellent work on implementing the subpoena update functionality!The method is correctly handling the following:
- Validation of the defender's choice and national ID.
- Fetching of lawyer details using the
LawyersServiceif a national ID is provided.- Making a PATCH request to update the subpoena with the updated details.
- Handling successful and error responses from the backend API.
The code is well-structured, readable, and follows best practices.
apps/judicial-system/backend/src/app/modules/defendant/defendant.service.ts (1)
206-220: LGTM!The added code segment enhances the error handling and robustness of the
updateByNationalIdmethod by ensuring that a valid defendant exists before attempting an update. It queries thedefendantModelusing both the formatted and original national IDs, providing flexibility in the lookup. If no defendant is found, it throws anInternalServerErrorExceptionwith a clear error message indicating the absence of the defendant for the specified case.This addition improves the overall reliability and maintainability of the service.
apps/judicial-system/backend/migrations/20240827132504-create-subpoena.js
Show resolved
Hide resolved
unakb
changed the title
apps/judicial-system/backend/migrations/20240827132504-create-subpoena.js
Show resolved
Hide resolved
apps/judicial-system/backend/src/app/modules/defendant/defendant.service.ts
Outdated
Show resolved
Hide resolved
apps/judicial-system/backend/src/app/modules/notification/notification.service.ts
Show resolved
Hide resolved
apps/judicial-system/backend/src/app/modules/subpoena/internalSubpoena.controller.ts
Outdated
Show resolved
Hide resolved
apps/judicial-system/backend/src/app/modules/subpoena/models/subpoena.model.ts
Show resolved
Hide resolved
apps/judicial-system/backend/src/app/modules/subpoena/subpoena.service.ts
Show resolved
Hide resolved
Asana
Asana
What
Checklist:
Summary by CodeRabbit
Release Notes
New Features
Subpoenamodule for managing subpoenas within the judicial system.Enhancements
Documentation