fix: keep default values that may have been set

[jenniferarnesen]

The i18next-scanner parser will set default values for a string if they are provided (including for plurals).

This fix will copy any default values into the json that is used to generate the en.pot file.

Then we can have code in our apps like this:

const likes = i18n.t(
    '{{count}} likes',
    { 
        count: numLikes,
        defaultValue: '{{count}} like',
        defaultValue_plural: '{{count}} likes'
    });

This results in the following in the en.pot file:

msgid "{{count}} likes"
msgid_plural "{{count}} likes"
msgstr[0] "{{count}} like"
msgstr[1] "{{count}} likes"

Ultimately in the app, we end up with these strings: 1 like and 2 likes as default.

[amcgee]

Looks good, let’s give this a shot!

[dhis2-bot]

🎉 This PR is included in version 4.0.3 🎉

The release is available on:

• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀