v1.2.0 - Exercise Saving Fix

🛠 Bug Fixes

• Fixed Issue with Muscle Engagements in Exercise Saving: Resolved a bug where exercises were being saved with unintended MuscleEngagement entries. Previously, MuscleEngagement entities were sometimes added for the same muscle with differing activation levels, even if these entries had not been explicitly provided. This fix ensures that only specified MuscleEngagement instances are associated with the exercise on save.

v1.1.0

Added

• Introduced the @CreatedResponseCode annotation to indicate successful resource creation in the API documentation for saveEquipment and saveExercise methods.

Changed

• Corrected validation issues by removing the @NotNull annotation from the ID field in the ExerciseEntity class.
• Updated the validation constraints for the name field in the ExerciseEntity and ExerciseRequestDTO classes to allow shorter names, changing the minimum length from 10 to 4 and the maximum length from 50 to 30.
• Enhanced the ValidationExceptionHandler to include a handler for HttpMessageNotReadableException, providing a clear response when the request body cannot be deserialized.

Removed

• Streamlined error handling by removing the ErrorResponseDTO class and replacing it with more standardized error responses.

v1.0.0

🚀 Release v1.0.0 - Gym Exercises API

Welcome to the initial release of Gym Exercises API! 🎉 This version establishes the core capabilities of the API for managing gym exercises, equipment, and user authentication. Here’s what’s included:

🌟 Main Features

1. Exercise Management

• Create, Update, Delete, and Retrieve Exercises: Manage detailed information about gym exercises, including descriptions, targeted muscle groups, and associated equipment.

2. Equipment Management

• Full CRUD Operations: Easily add, update, delete, and view gym equipment to keep exercise resources organized.

3. JWT-Based Authentication

• Secure API Access:
  • User Token: A unique token with expiration that regenerates for testing the API.
  • Developer Token: A token for performing non-GET operations, ensuring streamlined access for developers.

4. Pagination and Sorting

• Enhanced Data Handling: Access large datasets with pagination and sorting capabilities to control and optimize data responses.

5. Standardized Error Responses

• Consistent Error Handling: Unified error messaging throughout the API for a smooth and predictable client experience.

6. API Documentation

• Interactive Swagger Documentation: Easily navigate, test, and understand the API endpoints through the built-in Swagger interface.