Add REST Endpoint for DAC Application Approval with Validation and State Management

[Azher2Ali]

Summary

#117- Introduced a new REST endpoint that allows DAC (Data Access Committee) members to approve applications. This feature ensures robust state transitions, clear validations, and comprehensive user feedback.

Description of Changes

API

• New Endpoint: POST /applications/{applicationId}/approve

  • Allows DAC to approve applications one at a time.
  • Validates applicationId and approverId as required fields and ensures they are numbers.
  • Updates the state of an application to approved and integrates with the state transition machine.
  • Prevents modifications to approved applications by any user.

• Response:

  • Provides clear feedback on success or failure of approval.
  • Uses structured error handling with proper HTTP status codes and descriptive messages.

• Swagger Documentation:

  • Added comprehensive instructions for using the endpoint, including request/response formats and validation criteria.

Service

• Refined logic to handle state transitions robustly.
• Ensures the service prevents type-related errors and edge cases during the approval process.
• Updates application history to include:
  • Timestamp of approval.
  • Information about the approver.

Data Model

• Added support for storing approval metadata, including the approver’s details and approval timestamp.

Special Instructions

Before running these changes:

• Ensure all dependencies are up-to-date by running:

  pnpm i
  

[demariadaniel]

Do you have the Prettier extension installed? There are whitespace changes here which don't match what I'd expect to see

[Azher2Ali]

Missed adding Prettier under my extention list, will surely keep in mind for the next time. Thanks for noticing!

[demariadaniel]

a) new files need the Copyright at the top
b) We have ApplicationStateManager defined at https://github.com/Pan-Canadian-Genome-Library/daco/blob/main/apps/api/src/api/states.ts#L61
which extends functionality https://github.com/eram/typescript-fsm

including the .can method which could essentially perform the same function as this.
I would use the existing class and work within that framework.

Now, there may not be implementation examples for the State Machine yet in the API, except for in the unit tests: https://github.com/Pan-Canadian-Genome-Library/daco/blob/main/apps/api/tests/api/application-state.test.ts

So I can review this with you and show how Jon and I were intending to implement the state machine and action updates

[demariadaniel]

Off to a great start, handful of changes to iron out first

[demariadaniel]

approverId is unused here

[demariadaniel]

This can just be (!result.success) { return result }
The success, errors and message will already be populated by getApplicationById