You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fineract.apache.org by "Adam Saghy (Jira)" <ji...@apache.org> on 2025/05/12 10:33:00 UTC
[jira] [Resolved] (FINERACT-1965) Fineract uses "smart date resolvement"
[ https://issues.apache.org/jira/browse/FINERACT-1965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adam Saghy resolved FINERACT-1965.
----------------------------------
Resolution: Fixed
> Fineract uses "smart date resolvement"
> --------------------------------------
>
> Key: FINERACT-1965
> URL: https://issues.apache.org/jira/browse/FINERACT-1965
> Project: Apache Fineract
> Issue Type: Bug
> Reporter: Norbert Táskai
> Priority: Major
> Fix For: 1.9.0
>
>
> *Background*
> When Fineract parses dates coming from API request body, it uses smart resolvement, which means if the given date is not an existing date, then it will be resolved to the closest valid date ({{{}2023-06-31{}}} to {{{}2023-06-30{}}}).
> {panel}
> {panel}
> {panel}
> *Acceptance Criteria*
> * Invalid dates should be rejected on the API (http 400 - bad request)
> * This is validated by a few API call which uses date.
> * One integration test should be written
> {panel}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)