Opened 2 years ago
Closed 2 years ago
#34120 closed Bug (invalid)
Changing translations of model options and attributes is not detected as change in making migrations
| Reported by: | Sajjad Sanikhani | Owned by: | nobody |
|---|---|---|---|
| Component: | Migrations | Version: | 4.1 |
| Severity: | Normal | Keywords: | Translation, Migrations, Models, Locale |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description (last modified by )
After writing my model with its options, I made migrations.
Then I changed translation of model verbose name in *.po file and compiled it.
After that I supposed that executing makemigrations, add new migration file that contains new translated verbose name of that model. But it is not happened.
This problem is only with gettext_lazy, because this function return reference of translation in lazy mode. Thus it is not detected as change.
Change History (2)
comment:1 by , 2 years ago
| Description: | modified (diff) |
|---|
comment:2 by , 2 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
The migration system doesn't consider translations. It's done by design, as translations shouldn't affect the database structure.