-
-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Finer granularity error codes in order to support i18nized errors from the server #377
Labels
A-Client-Server
Issues affecting the CS API
feature
Suggestion for a significant extension which needs considerable consideration
Comments
More granular error codes are spread out over quite a few issues in the repo ftr. |
turt2live
added
feature
Suggestion for a significant extension which needs considerable consideration
A-Client-Server
Issues affecting the CS API
labels
Sep 12, 2018
You already started doing it with M_ errors - please just do it across the board. Just adding l10n to the server is unlikely to be much beneficial as there's more than one homeserver implementation anyway; I'd say that it's a good work for client SDKs. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-Client-Server
Issues affecting the CS API
feature
Suggestion for a significant extension which needs considerable consideration
Right now there are many APIs where we return a generic 400,403,404 etc with a human readable error in English but no finer-granularity error code which a client could pick up and present a proper i18nized error message. Surely we need some kind of solution for this - whether it's either mandating servers do the i18n for errors themselves based on Accept language headers, or having much more sophisticated and finer granularity errors.
A good example is the groups API:
Where clients will not only want to i18nize but also s/group/communities/ for presentation to the user (see element-hq/element-web#6003).
Related: https:/matrix-org/matrix-doc/issues/1638 and https:/matrix-org/matrix-doc/issues/603
The text was updated successfully, but these errors were encountered: