AshharAhmadKhan opened a new pull request, #6043:
URL: https://github.com/apache/fineract/pull/6043

   JIRA: https://issues.apache.org/jira/browse/FINERACT-2501
   
   This PR is a continuation of the work started in #5597, #5744, and #6042, 
which addressed the instability of auto-generated Feign client method names 
caused by Swagger deduplication numbers shifting when new endpoints are added.
   
   This PR covers the Infrastructure, Organisation, and User Management 
modules, adding explicit operationId values to all endpoints that were missing 
them. The naming convention follows the same pattern established in the 
previous PRs: methodName + EntityName + DescriptionClause (for example, 
retrieveAllHolidays, handleCommandsScheduler, updateRolePermissions).
   
   Files changed:
   
   - AccountNumberFormatsApiResource (6 operationIds added)
   - CodesApiResource (6 operationIds added)
   - ExternalServicesConfigurationApiResource (2 operationIds added)
   - EntityDatatableChecksApiResource (4 operationIds added)
   - HookApiResource (6 operationIds added)
   - InstanceModeApiResource (1 operationId added)
   - InlineJobApiResource (1 operationId added)
   - SchedulerApiResource (2 operationIds added)
   - SurveyApiResource (3 operationIds added)
   - HolidaysApiResource (6 operationIds added)
   - OfficesApiResource (7 operationIds added)
   - ProvisioningCriteriaApiResource (5 operationIds added)
   - StaffApiResource (2 operationIds added)
   - WorkingDaysApiResource (3 operationIds added)
   - ForgotPasswordApiResource (1 operationId added)
   - PasswordPreferencesApiResource (3 operationIds added)
   - PermissionsApiResource (2 operationIds added)
   - RolesApiResource (9 operationIds added)
   - UsersApiResource (2 operationIds added)


-- 
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