You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running extract-messages -l=en,nb -o src/translations -d nb --flat true --overwriteDefault false 'src/**/*.{ts,tsx}' does actually generate the ids with the filename:
"navigation.TabNavigator.profile": "Profil",
But React.Intl complains about a missing translation with the id used in formatMessage:
(notice the lack of filename in the id)
What is the expected behavior?:
The id used in formatMessage, FormattedMessage etc, includes the filename when filebase is set to true.
Suggested solution:
Not sure what the issue is yet, if it is some fault of mine or an actual bug.
The text was updated successfully, but these errors were encountered:
node
version: v10.16.3yarn
version: 1.22.4Do you want to request a feature or report a bug?:
Bug
What is the current behavior?:
To avoid id collisions I'd like to generate ids using the filename, so I've set
filebase: true
inbabel.config.js
:Used like this in the
TabNavigator
-component:Running
extract-messages -l=en,nb -o src/translations -d nb --flat true --overwriteDefault false 'src/**/*.{ts,tsx}'
does actually generate the ids with the filename:But
React.Intl
complains about a missing translation with the id used informatMessage
:(notice the lack of filename in the id)
What is the expected behavior?:
The id used in
formatMessage
,FormattedMessage
etc, includes the filename whenfilebase
is set totrue
.Suggested solution:
Not sure what the issue is yet, if it is some fault of mine or an actual bug.
The text was updated successfully, but these errors were encountered: