itsmenewbie03 / appt-cert-gen-api Goto Github PK

what to do

• add an endpoint that would take a template file and the props it needs including if is it paid or not, this endpoint will store the template file and add a document in the documents collection
• this will require update in the document model as this will add a new prop to the documents.

what to do

• in connection to #1 the endpoint must be updated to properly handle paid and free document
• the endpoint should enforce that the user should explicitly add or_number in required_data

what to do?

• implement the address prop for the resident data model, this will require us to modify the model and all the necessary implementation

what to do?

• implement an endpoint to allow the admin to delete an upload document template

what to do?

• this endpoint must return all the appointment that belongs to the user
• this will allow the FE to display all the users appointment in a list

what to do?

• implement external api to validate email address along with their domain
• this is not a fool proof method but this should be better than nothing

what to do?

• implement an endpoint the would allow the admin to handle walk-in appointments and should be able to generate certificates for them.

REGRESSION: caused by f065d8d

what to do

• the DROPBOX_ACCESS_TOKEN stored in .env is short-lived and dropbox don't support generating long-lived token, so we need to implement it as they intend us to do.
• this ensures #1 will not cause issues as we go

what to do

• This endpoint should allow generation of certificate for a registered user.
• Another endpoint would explicitly handle walk-in appointments

what to do?

• send a notification to user when an update to their appointment is made
• the user should be able to mark notification as read

what to do?

• implement the price prop in paid documents this will require to modify the model along with all the implementations

The endpoint should validate that the template does have at least 1 placeholder.

#12 is closed, however it only implements validations in the create. the same validations added should also be implemented in updates.

The following validation should be implemented

• prevent duplicate resident entry by checking resident database before creating a new resident

• ensure birthday input are sensible