getodk / getodk/central

Localize additional Problem messages

Open
#489 0 comments 0 reactions 0 assignees View on GitHub
frontend
Dominant language
JavaScript
Stars
226
Forks
235
Avg merge
2d 22h
Merged PRs (30d)
19

Description

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.
- [ ] 403.1. "The authentication you provided does not have rights to perform that action."
- This can be shown after submitting a Web Form in the case described here: #1001
- [x] 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.
- Done in getodk/central-frontend#952

Whoever works on this issue should take another look at lib/util/problem.js for other Problems that would be worth localizing.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.