-
Notifications
You must be signed in to change notification settings - Fork 5
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
Standardize on 'en', not 'en-US' as a language code, but register both #868
Conversation
Coverage Report
File Coverage
|
}); | ||
|
||
// handle two-part locales | ||
register("en-US", () => import("@/langs/json/en.json")); | ||
register("en-GB", () => import("@/langs/json/en.json")); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to handle other two part locales? Spanish is spoken in a lot of countries.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure these are strictly necessary. I think part of the issue was that we were defaulting (in hooks.server.ts
) to en-US
and that wasn't registered.
✅ Deploy Preview for documentcloud-frontend ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Suspect IssuesThis pull request was deployed and Sentry observed the following issues:
Did you find this useful? React with a 👍 or 👎 |
Trying to solve #818
My browser sets the
accept-language
header andwindow.navigator.language
toen-US
, but we weren't registering that as a locale, onlyen
. So this adds that registration and also standardizes our own setting toen
.