This makes it easier to add custom translations in projects using this app.
For some reason, Django generates a new migration even when the verbose_name is changed. However, I didn't know if you want the updates to be added to the previous migrations, have it in a separate migration or automatically squashed. Currently it is the default with a new, separate migration file
Coverage increased (+0.04%) to 97.996% when pulling 2ff2e55c6559d18a39fd997dd7707ec7a03fa0dd on OskarPersson:verbose-names into c8698d0e2c866af9360b3ca9992d8e8d658c8ac4 on vittoriozamboni:master.
Coverage increased (+0.04%) to 97.996% when pulling 2ff2e55c6559d18a39fd997dd7707ec7a03fa0dd on OskarPersson:verbose-names into c8698d0e2c866af9360b3ca9992d8e8d658c8ac4 on vittoriozamboni:master.
Coverage increased (+0.04%) to 97.996% when pulling 2ff2e55c6559d18a39fd997dd7707ec7a03fa0dd on OskarPersson:verbose-names into c8698d0e2c866af9360b3ca9992d8e8d658c8ac4 on vittoriozamboni:master.
Coverage increased (+0.04%) to 97.996% when pulling 2ff2e55c6559d18a39fd997dd7707ec7a03fa0dd on OskarPersson:verbose-names into c8698d0e2c866af9360b3ca9992d8e8d658c8ac4 on vittoriozamboni:master.
This makes it easier to add custom translations in projects using this app.
For some reason, Django generates a new migration even when the
verbose_name
is changed. However, I didn't know if you want the updates to be added to the previous migrations, have it in a separate migration or automatically squashed. Currently it is the default with a new, separate migration file