Release/v0.3.0

[jhonatapers]

This pull request introduces a new feature to provide an aggregated summary of drive quotas, including total allocated, used, and available quotas, as well as the total number of members. It also includes several supporting changes, such as API additions, gateway and repository enhancements, and some naming corrections for consistency.

New Quota Summary Feature

• Added the GetQuotasSummaryUseCase and its implementation DefaultGetQuotasSummaryUseCase to calculate the total number of members, total allocated quota, total used storage, and total available quota. [1] [2] [3]
• Introduced a new API endpoint in MemberAdminAPI and its controller to expose the quota summary, returning a QuotaSummaryResponse. [1] [2] [3]

Gateway and Repository Enhancements

• Extended the MemberGateway and FileGateway interfaces and their implementations to support counting members, summing all quotas, and summing all file content sizes. [1] [2] [3] [4] [5] [6]
• Added new methods in JPA repositories (FileJpaRepository, MemberJpaRepository) to support these summary operations.

API and Model Naming Consistency

• Standardized the spelling of "amount" (previously "ammount") in API documentation, request/response models, and entity fields for clarity and consistency. [1] [2] [3] [4] [5] [6] [7]

Configuration Updates

• Registered the new use case in the Spring configuration to ensure it is available for dependency injection. [1] [2]

Supporting Model and Import Changes

• Added new response models and updated imports to support the new summary endpoint and its integration. [1] [2] [3]

These changes collectively introduce a comprehensive quota summary feature for administrators, while also improving code clarity and maintainability.