[
https://issues.apache.org/jira/browse/FINERACT-2196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Saghy resolved FINERACT-2196.
----------------------------------
Resolution: Fixed
> API fetch config by name returns 500 for invalid config name
> ------------------------------------------------------------
>
> Key: FINERACT-2196
> URL: https://issues.apache.org/jira/browse/FINERACT-2196
> Project: Apache Fineract
> Issue Type: Bug
> Affects Versions: 1.11.0
> Reporter: Adam Saghy
> Priority: Major
> Fix For: 1.12.0
>
>
> When we log in to the Fineract UI, we receive several general error message
> saying “internal server error”.
> Looking in to the developer tool it can been seen that the following API call
> receives a 500 error response:
> * Fetch global configuration entry by name
> ** GET {{{}url{}}}/configurations/name/enable_business_date
> * Similarly the application fails with HTTP 500, if a none existing id was
> provided
> ** GET {{{}url{}}}/configurations/999
> The correct response code would be 404 since the configuration does not exist
> with this name!
> This feature was introduced lately
> [https://github.com/apache/fineract/pull/4057]
> *Acceptance criteria*
> * If the global configuration does not exists with the name, Fineract should
> raise proper exception
> ** fetch by name 404 → Configuration property `" + propertyName + "` does
> not exist"
> ** fetch by id 404 → Configuration identifier `" + configId + "` does not
> exist
> * Add proper testing
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
