josdem/vetlog-backend

AI Summary: Configure SonarCloud for the Vetlog backend/API project to enable code coverage detection. This involves setting up the project to run tests with `jacocoTestReport sonarqube` without errors, ensuring SonarCloud correctly detects the coverage, and updating the project's README with the necessary information.

AI Summary: Configure Swagger UI for the Vetlog backend API to enable interactive API documentation, allowing users to view API specifications and test endpoints directly within the Swagger interface. All existing tests must remain passing after the configuration.

AI Summary: Implement GitHub Actions workflows to automate testing. The workflows should trigger tests on pull requests and pushes to the main branch, ensuring all tests pass before merging.

AI Summary: Implement a global exception handler in the Vetlog backend controllers using Spring's `@ExceptionHandler` annotation. This should prevent the need for individual error handling in each controller method. Comprehensive unit tests are required to ensure functionality.

AI Summary: Replace existing command classes in the Vetlog backend/API with Java records. This involves refactoring code to utilize Java records, ensuring all functionality remains intact and tests pass.

AI Summary: Create a README file for the Vetlog backend/API project. The README should include instructions on how to run, build, test, and execute the project. Referencing the provided Gmailer project's README as an example is recommended.

AI Summary: Implement Spring AOP in the Vetlog backend API to handle exceptions thrown in the services package. This involves configuring AOP to catch exceptions, provide a centralized error handling mechanism, and ensure all existing tests continue to pass.

AI Summary: Configure Jacoco for generating test coverage reports in the Vetlog backend/API project. This involves setting up the `jacocoTestReport` task in the build script (likely Gradle or Maven), ensuring it runs without errors, and generating reports viewable within the project. Finally, update the project's README to reflect the new coverage reporting capabilities.