-
Notifications
You must be signed in to change notification settings - Fork 1
Add backward compatibility for translation keys #789
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
base: develop
Are you sure you want to change the base?
Conversation
Summary of ChangesHello @german664, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request significantly enhances the Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
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.
Code Review
This pull request introduces backward compatibility for translation keys by loading a swapConfig from CDN with a local fallback. It also includes tests to ensure the backward compatibility works as expected. The review focuses on potential issues related to error handling, and code clarity.
16f56e0
to
6920a83
Compare
# Conflicts: # src/assets/translations/en-US.instructions.json # src/assets/translations/en-US.json # src/components/external/CapitalOffer/components/CapitalOffer/CapitalOffer.tsx # src/components/external/CapitalOverview/components/CapitalOverview/CapitalOverview.tsx # src/components/external/CapitalOverview/components/GrantItem/GrantItem.tsx # src/components/external/CapitalOverview/components/GrantList/GrantsDisplay.tsx # src/config/translations/swapConfig.json
d69dabd
to
c61acb0
Compare
08a381d
to
f0bdff7
Compare
Size Change: +11.7 kB (+3.67%) Total Size: 330 kB
ℹ️ View Unchanged
|
Summary
This implementation provides backward compatibility for translation keys that have been renamed, allowing users to continue using old keys in their custom translations without breaking their applications.
When
get(key)
is called:swapConfig
and the old key is different.Note: array mappings are currently skipped. This is preserved in the swap config for internal use, but will be treated as a new key.