Closed PcNerd9 closed 2 weeks ago
Appears VERY duplicated
you commented on the previous issue created for this feature that the issue should be divided into two:
Can you link both issues and I will review asap
https://github.com/hngprojects/hng_boilerplate_nestjs/issues/254#issue-2418183784
link to the issue that implement the sending of the email in the background using Celery
and RabbitMq
I have seen both. Can you explain the difference because I dont see it? @PcNerd9
Below is the link of the original issue where mark commented on saying that i should split into two tickets. https://github.com/hngprojects/hng_boilerplate_nestjs/issues/242#issue-2417496562 Hope this answer your question sir @highb33kay
Description
Develop an endpoint to handle requests for sending emails using pre-defined templates. The emails should be placed in a database queue for sending to ensure the application remains responsive. The endpoint should handle variable substitution, replacing placeholders in the templates with actual data.
Acceptance Criteria
Data Validation
template_id
,recipient
, andvariables
fields are provided and correctly formatted.Authentication and Authorization
Error Handling
Performance and Security
Documentation
Testing Requirements
Dependencies and Impact
Requirements
Expected Outcome
Endpoints
[POST] /api/v1/send-email
Error Responses: Status Code:
500 Internal Server Error
Body:status Code:
404 Not Found
Body:Status Code:
405 Method Not Allowed
Body:Status Code:
400 Bad Request
Body:Testing
Test Scenarios
Successful Email Sending Request
202 Accepted
.Template Not Found
404 Not Found
.Internal Server Error
500 Internal Server Error
status code.Invalid Method
405 Method Not Allowed
status code.Bad Request
400 Bad Request
status code.LINKS
link to the issue that implement the sending of the email in the background using
Celery
andRabbitMq
https://github.com/hngprojects/hng_boilerplate_nestjs/issues/254#issue-2418183784