Only store missing translations in database, and remove after export

[rvanlaak]

I was thinking about a scenario how we can easily keep track of missing translations. What happened was that I've modified the key of a translation in the translation file, but did not change it in the view. Because I've imported all translations into the database earlier, the view still seems to look fine because the translation was in the database.

Would it be possible to:

• Only store missing keys in the database while "browsing" the application,
• then export those keys after translating them, and thereafter remove them from the database,
• and finally commit changed keys to VCS, and update application, so the process can start over again?

That way we don't have to enable the bundle in our production environment. Or does this sound as a really weird scenario?

[cedric-g]

It does not sound weird to me, I suppose people that use the bundle only in dev manage translations as a similar way. But to get this exact flow it would required to add a new option to the import command and, and maybe also update the export command.

[rvanlaak]

Can you identify some actionables, so I can dive into that? I'll put the PR on the separate branch we already had.

[Pierstoval]

Is this issue related to the list_missing_translations branch?

If yes, rebase + PR could be easier for code reviews