Endpoints to CRUD Nigerian Youth Voices

[chidioguejiofor]

Description

As a user, I should be able to:

• hit the POST /api/nigerian-youth-voices/ endpoint so that I can create a new Nigerian youth voice
• hit the GET /api/nigerian-youth-voices/ endpoint so that I retrieve all Nigerian youth voices
• hit the PUT /api/nigerian-youth-voices/:id endpoint so that I can edit/change a particular Nigerian youth voices
• hit the DELETE /api/nigerian-youth-voices/:id endpoint so that I can edit/change a particular Nigerian youth voices

Technical Detail

The data for the events endpoint should have the following structure:

• title
• description
• createdAt
• updatedAt
• imageURL

• The data should be written to a local file system using the FileService

Acceptance Criteria

• [ ] When a user hits the POST, DELETE, PUT, and GET methods with valid data he gets a successful response
• [ ] When a user hits the POST, DELETE, or PUT with invalid data, he should get a 400 status code with details of the error as follows:

  
  {
  "message": "Validation Error",
  "errors": {
      "title": ["is required"],
       "description": ["is required"],
  }

}

 - [ ] When the id is not found when updating or deleting a Nigerian Youth Voice then it should return 404 with an appropriate message

[chidioguejiofor]

This one looks good enough