The motivation and requirements for this use-case are described in this thread; it will serve as the first point of contact between the potential service providers and the microservice.
This endpoint should be protected (i.e, require a user login) but this is not necessary to complete the majority of the work required. We can add route protection following the removal of Passport-JWT.
The controller and use-case should be sufficiently unit tested.
The motivation and requirements for this use-case are described in this thread; it will serve as the first point of contact between the potential service providers and the microservice.
This endpoint should be protected (i.e, require a user login) but this is not necessary to complete the majority of the work required. We can add route protection following the removal of Passport-JWT.
The controller and use-case should be sufficiently unit tested.