mgr/dashboard: Avoid merge conflicts in messages.xlf by auto-generating it at build time?
Currently, the file ./src/pybind/mgr/dashboard/frontend/src/locale/messages.xlf needs to be updated by running "npm run i18n" every time when changes to the UI have been made that affect translatable strings. The modified messages.xlf file then needs to be commited and is part of the changeset. This approach has several issues:
- As this file potentially gets modified by many pull requests, it becomes a "hot spot", requiring lots of rebasing and resolving of conflicts
- Including the messages.xlf file in the same commit as other changes makes it more difficult to back-port such a change to older releases, where the messages.xlf might differ significantly
Would it make sense to treat this file as an asset that gets generated at build time instead, taking it out of git revision control?