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
Many Backend Problems aren't shown in Frontend or are extreme edge cases. However, we want to localize Problem messages that are more likely to be shown in Frontend. That localization will be done in Frontend. From a quick look at lib/util/problem.js in Backend, I see a few messages that I think would be worth localizing:
400.17. "The form you have uploaded attempts to change the type of the field at ${path}. …"
I this is only shown in the FormNew component in Frontend, so we could add an i18n message there.
400.12. "Could not perform decryption. Double check your passphrase and your data and try again."
This is only shown in the SubmissionDownload component, so we could add an i18n message there.
404.1. "Could not find the resource you were looking for."
This is shown if the user navigates to a resource that used to exist, but has since been deleted. Maybe the user bookmarked a page. This message is not specific to any particular component. Maybe we should handle it specially in requestAlertMessage() in Frontend.
Many Backend Problems aren't shown in Frontend or are extreme edge cases. However, we want to localize Problem messages that are more likely to be shown in Frontend. That localization will be done in Frontend. From a quick look at lib/util/problem.js in Backend, I see a few messages that I think would be worth localizing:
FormNew
component in Frontend, so we could add an i18n message there.SubmissionDownload
component, so we could add an i18n message there.requestAlertMessage()
in Frontend.Whoever works on this issue should take another look at lib/util/problem.js for other Problems that would be worth localizing.
The text was updated successfully, but these errors were encountered: