-
Notifications
You must be signed in to change notification settings - Fork 168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Option to provide non translated strings in a fallback locale #1659
Option to provide non translated strings in a fallback locale #1659
Conversation
🦋 Changeset detectedLatest commit: cc35708 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
@thebigrick is attempting to deploy a commit to the BigCommerce Platform Team on Vercel. A member of the Team first needs to authorize it. |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Looks good, can we add a changeset please? |
I just provided one. I opted for a minor change rather than a patch since I do not consider the previous behavior a bug. |
We assume 'en' as the most complete language
1a841f8
to
cc35708
Compare
…#1672) Co-authored-by: Riccardo Tempesta (aka The BigRick) <[email protected]>
What/Why?
If a new string is added, the translation must be available in any language. If not, the dotted path notation will be displayed in its place. I introduced the capability of using a fallback language for the missing strings.
Testing
messages/en.json
fileen