cli/extract: update source translations

This is obviously only relevant when using messages with custom IDs.

Right now if we extract messages and then decide to update them (in source code) and run extract again - it won’t update the messages in catalog. It will leave initial strings and there’d be no way to update them other than manually edit the catalog.

I think it shouldn’t be like that and we should update source catalog with updated messages in this case.

We can change this string:

translation: prevCatalog[key].translation,

to

translation: config.sourceLocale === locale ? nextCatalog[key].defaults : prevCatalog[key].translation,

And this leads to another issue 😃 (I wrote about it here) - when using minimal format with custom IDs, it extracts as 'message.id': 'message.id' instead of 'message.id': 'default message' This can be fixed here, changing:

translation: config.sourceLocale === locale ? key : "",

to

translation: config.sourceLocale === locale ? message.defaults : "",

What do you think?

[tricoder42]

Fixed and released in v2.2.0. Thanks to all involved!

[tricoder42]

Alright, just to narrow the problem down. This is related only to message catalog for sourceLocale in minimal format. I think --overwrite makes more sense than --update-defaults.