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
Normalize translation domain #10728
Normalize translation domain #10728
Conversation
Thanks for making a pull request to JupyterLab! To try out this branch on binder, follow this link: |
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.
LGTM, thanks!
Thanks ! Should we backport this @fcollonval ? |
It may be a good idea to do it. Should it be backported to 3.0.x and 3.1.x? |
I would say yes! |
@meeseeksdev please backport to 3.1.x |
@meeseeksdev please backport to 3.0.x |
Co-authored-by: Frédéric Collonval <fcollonval@gmail.com>
Co-authored-by: Frédéric Collonval <fcollonval@gmail.com>
References
Translation files are normalized. But the domain that reference it in the frontend is not. This breaks the ability to load translation if the domain requested is not normalized.
Code changes
Domain is automatically normalized to be tolerant to extension authors not knowing the correct normalization rule.
User-facing changes
N/A
Backwards-incompatible changes
N/A