Ambika-Sony opened a new pull request, #5665:
URL: https://github.com/apache/fineract/pull/5665

   
   This Pull Request standardizes the operationId naming conventions within the 
Savings module API resources (SavingsAccountsApiResource.java).
   
   By providing explicit and unique operationId values in the @Operation 
Swagger annotations, we ensure that client-side SDKs (like the Fineract Java 
and TypeScript clients) generate clean, predictable, and user-friendly method 
names.
   
   Key Technical Achievements
   Architectural Migration: Successfully transitioned the standardization logic 
from the legacy fineract-provider structure into the new 1.15.0-SNAPSHOT 
modular architecture.
   
   Upstream Synchronization: Performed a manual rebase against upstream/develop 
to resolve complex conflicts in GitHub workflows and the newly created 
fineract-savings sub-module.
   
   Structural Integrity: Resolved JPA configuration path conflicts 
(persistence.xml) across multiple modules (fineract-loan, fineract-cob, 
fineract-investor) caused by the recent project refactor.
   
   Clean History: Utilized a git reset --soft workflow to ensure a single, 
clean, and high-quality commit on top of the latest project state.
   
   Verification Results
   Local Build: Verified with ./gradlew :fineract-savings:compileJava — BUILD 
SUCCESSFUL.
   
   Static Analysis: Verified that the new module paths are correctly mapped and 
that no new checkstyle violations were introduced in the Savings API resource.
   
   Parity: Confirmed that all operationId values align with the patterns used 
in other standardized modules.
   
   Checklist
   [x] Write the commit message as per our guidelines.
   
   [x] Acknowledge that we will not review PRs that are not passing the build 
("green").
   
   [x] Follow our coding conventions.
   
   [x] This PR is focused on a single task (Savings API standardization).


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to