[
https://issues.apache.org/jira/browse/FINERACT-2585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hemanth Madhav resolved FINERACT-2585.
--------------------------------------
Fix Version/s: 1.11.0
Resolution: Fixed
The proposed changes have been implemented and successfully merged into the
develop branch via {*}Pull Request #5758{*}.
This fix standardizes locale dependent string case conversions across core
command processing and build services, ensuring environmental consistency and
preventing functional failures in locales with unique casing rules (e.g., the
'Turkish I' issue).
Closing as fixed
> Standardize String Locale usage in Command Infrastructure and Build Services
> ----------------------------------------------------------------------------
>
> Key: FINERACT-2585
> URL: https://issues.apache.org/jira/browse/FINERACT-2585
> Project: Apache Fineract
> Issue Type: Bug
> Components: Build
> Affects Versions: 1.14.0
> Reporter: Hemanth Madhav
> Priority: Major
> Fix For: 1.11.0
>
>
> As a follow-up to architectural hardening and I18n standardization
> (referencing FINERACT-2538), I have identified several instances of
> locale-dependent string case conversions in critical command-handling
> infrastructure.
> Specifically, {{CommandWrapperBuilder}} and {{CommandSourceService}} use
> default locale {{.toUpperCase()}} calls, which can lead to command
> mismatching in certain system environments (e.g., Turkish locale 'i' vs 'I'
> issues).
> Additionally, I found a similar instance in {{GpgService.groovy}} within the
> buildSrc. I propose standardizing these to use {{Locale.ROOT}} to ensure
> consistent behavior across all deployment environments
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
