feat: add project-wide i18n support#209
Conversation
|
There were a lot of files changed, very hard to look at everything, but in general looks fine from my point of view. Don't forget to add docstrings and specify which files you said were incorrectly merged |
| }, | ||
|
|
||
| async down(queryInterface, Sequelize) { | ||
| // Intentionally left as no-op because original free-text values were not uniquely preserved. |
There was a problem hiding this comment.
Is there any way that we can avoid breaking undoing of migrations? Once we run these migrations we cannot go back to a previous version of the app.
| }, | ||
|
|
||
| async down(queryInterface, Sequelize) { | ||
| // No-op: reverse mapping is intentionally omitted. |
There was a problem hiding this comment.
Same as mentioned before
| }, | ||
|
|
||
| async down(queryInterface, Sequelize) { | ||
| // No-op: reverse mapping intentionally omitted. |
The commit where I adapted the first ~100 files and where old logic was accidentally merged is:
This was the part where I initially tried to port changes that looked safe, but later noticed that some old logic had been brought back unintentionally. Because of that, I manually re-checked these files afterwards against the current (caution, a lot of files) Full list of files included in this commit |
Closes #155
Adapts the project to the existing i18n setup across the frontend, including dashboard views, modals, navigation, model-driven forms, validation messages, and backend-provided messages.