You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The ‘name’ of the locale in the error message is incorrect given a dictionary has been created and the management API endpoint is called again, but in the request, only the locale ‘name’ is changed.
Steps to reproduce 1. Call the Management API to create a locale (locale=en name=qa) 2. The locale is created 3. Now call the same endpoint but change the name only (name=qatest)
Actual result - We are showing the name inputted in the request
Expected result
We should display in the message the name of the dictionary already created for that specific locale
For example:
"message": "An i18n dictionary already exists for en",
"http_status": 400
The response code should be 400 Bad Request
The text was updated successfully, but these errors were encountered:
exalate-issue-syncbot
changed the title
AM - Management - Error message is n
AM - Management - Incorrect 'name' of locale displaying in error message
Mar 13, 2023
exalate-issue-syncbot
changed the title
AM - Management - Incorrect 'name' of locale displaying in error message
AM - Management - Incorrect locale 'name' displaying in response error message
Mar 13, 2023
exalate-issue-syncbot
changed the title
AM - Management - Incorrect locale 'name' displaying in response error message
Management - Incorrect locale 'name' displaying in response error message
Mar 20, 2023
The ‘name’ of the locale in the error message is incorrect given a dictionary has been created and the management API endpoint is called again, but in the request, only the locale ‘name’ is changed.
Steps to reproduce 1. Call the Management API to create a locale (locale=en name=qa) 2. The locale is created 3. Now call the same endpoint but change the name only (name=qatest)
Actual result - We are showing the name inputted in the request
Expected result
For example:
The text was updated successfully, but these errors were encountered: