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
Currently, the server responds with plain text English for errors (and without the Accept header should continue to do so for backwards compatibility).
I propose standardising error responses like so:
{
"status": 403,
"message": "User is not a VIP."
"translationKey": "__TranslationKey__"
}
The text was updated successfully, but these errors were encountered:
Joe-Dowd
changed the title
Feature Proposal: Server responses should include a key for translations is accept header is application/json
Feature Proposal: Server responses should include a key for translations if accept header is application/json
Aug 30, 2020
Seems like the API should provide the translation when using the standard "accept-language" header.
The key is only useful if the extension already knows about the error.
Currently, the server responds with plain text English for errors (and without the Accept header should continue to do so for backwards compatibility).
I propose standardising error responses like so:
The text was updated successfully, but these errors were encountered: