paulrps / library-api Goto Github PK

create the following endpoints to Category resource (/categories):

• GET /categories - returns all Categories as a list and status 200
• GET /categories/{:id} - returns one Category by ID and status 200
• POST /categories - create an Category passing the Category object on body and returns the generated ID and status 201
• PUT /categories - update an existing Category by passing on body the Author object with its ID and returns status 204
• DELETE /categories/{id} - delete an existing Category by ID and returns 204

When finish, attach the API definition on this issue. Use this site to create the API definition: https://editor-next.swagger.io/

create the spring project on site https://start.spring.io/ by setting:

project: Maven
language: Java
group: br.com
artifact: library-api
name: library api
description: An API to manage a library
packaging: Jar
Java: 17

It should be added the following dependencies:

Spring Data MongoDB (NoSql)
Spring Web
Spring Boot DevTools

following the /swagger/books.json file, that represents the API definition, create the controller for that resource to handle the client's requests on the base path /books (e.g. GET /books/79sdf79s7df9s7s - to get only one book by ID).

See the project specification (https://drive.google.com/file/d/1cPrfzJbUrndb_st2YDvhn7ub6dxqCnM8/view?usp=sharing) to follow the folder structure.

The goal is only to create the controller file with all endpoints defined on /swagger/books.json

create the following endpoints to Author resource (/authors):

• GET /authors - returns all authors as a list and status 200
• GET /authors/{:id} - returns one author by ID and status 200
• POST /authors - create an Author passing the Author object on body and returns the generated ID and status 201
• PUT /authors - update an existing Author by passing on body the Author object with its ID and returns status 204
• DELETE /authors/{id} - delete an existing Author by ID and returns 204

When finish, attach the API definition on this issue. Use this site to create the API definition: https://editor-next.swagger.io/

following the /swagger/authors.json file, that represents the API definition, create the controller for that resource to handle the client's requests on the base path /authors (e.g. GET /authors/79sdf79s7df9s7s - to get only one author by ID).

See the project specification (https://drive.google.com/file/d/1cPrfzJbUrndb_st2YDvhn7ub6dxqCnM8/view?usp=sharing) to follow the folder structure.

The goal is only to create the controller file with all endpoints defined on /swagger/authors.json

• GET /books - returns all Books as a list and status 200
• GET /books/{:id} - returns one Book by ID and status 200
• POST /books - create a Book passing the Book object on body and returns the generated ID and status 201
• PUT /books - update an existing Book by passing on body the Book object with its ID and returns status 204
• DELETE /books/{id} - delete an existing Book by ID and returns 204

When finish, attach the API definition on this issue. Use this site to create the API definition: https://editor-next.swagger.io/

following the /swagger/categories.json file, that represents the API definition, create the controller for that resource to handle the client's requests on the base path /categories (e.g. GET /categories/79sdf79s7df9s7s - to get only one category by ID).

See the project specification (https://drive.google.com/file/d/1cPrfzJbUrndb_st2YDvhn7ub6dxqCnM8/view?usp=sharing) to follow the folder structure.

The goal is only to create the controller file with all endpoints defined on /swagger/categories.json