ajayjha5899/oms

Order Management System POC

oms's Issues

CRUD implementation for Item entity

Implement CRUD operations on the Item entity with suitable APIs with correct error/exception handling and unit/integration tests.

Below are the list of tasks that can be check marked as and when they are completed.

• 1. GET /item - by name (text search), id, price
• 2. POST /item
• 3. PUT /item
• 4. DEL /item

Only unexpected exceptions to be handled in ExceptionController

Currently even the expected validation are throwing custom exceptions begin consumed by the ExceptionHandler, which I think is not the correct implementation.

There should be a helper class returning specific HTTP code responses and all the services should have this class autowired and validation failures should use the methods in this class to return an appropriate response.

Change dependency manager from Maven to Gradle

The project was initially created using Maven for dependency management. This should be changed to gradle, since it's clearly better lol.

Implement Redis caching wherever applicable in APIs supporting the Item entity

Redis caching needs to be implemented on the APIs for the Item entity wherever applicable.

Add SonarQube scan and test cases execution for all PRs to major branches using GitHub Actions

Pretty much the title.

Refer this.

All search APIs should be implemented using Spring Data Specification

Search or http GET APIs accepting multiple parameters should use Spring Data Specifications.

Refer Specifications Documentation

Add test cases with >95% coverage

Test cases need to be added for all the functionalities. Keep in mind that both unit test cases and integration test cases need to be written and the coverage should be >95%.

DTO validations should be done using Validator Interface

All the DTO validations/other object validations should be done using Spring's Validator interface.

Refer: Validation by Using Spring’s Validator Interface