Skip to content

refactor: migrate i18n.js to TypeScript as i18n.ts #601

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

blazethunderstorm
Copy link

@blazethunderstorm blazethunderstorm commented Jun 15, 2025

Fixes #414

Describe the changes you have made in this PR -

converted the i18n.js file to i18n.ts file as asked in issue

Note: Please check Allow edits from maintainers. if you would like us to assist in the PR.

Summary by CodeRabbit

  • Refactor
    • Updated internationalization support to improve locale detection and error handling for missing translations.
    • Enhanced fallback behavior to ensure English is used when localized messages are unavailable.

Copy link
Contributor

coderabbitai bot commented Jun 15, 2025

Walkthrough

The changes replace the JavaScript implementation of the internationalization (i18n) module in src/simulator/src/i18n.js with a new TypeScript version in src/simulator/src/i18n.ts. The new module maintains the same functionality using the banana-i18n library, handling locale detection, message loading, and fallback logic.

Changes

File(s) Change Summary
src/simulator/src/i18n.js Removed the JavaScript i18n module implementation.
src/simulator/src/i18n.ts Added a TypeScript i18n module with equivalent functionality, including locale and fallback logic.

Assessment against linked issues

Objective Addressed Explanation
Migrate /simulator/src/i18n.js to TypeScript (#414)

Assessment against linked issues: Out-of-scope changes

No out-of-scope changes were found.

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

npm error Exit handler never called!
npm error This is an error with npm itself. Please report this error at:
npm error https://github.com/npm/cli/issues
npm error A complete log of this run can be found in: /.npm/_logs/2025-06-15T13_13_30_119Z-debug-0.log

✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

netlify bot commented Jun 15, 2025

Deploy Preview for circuitverse ready!

Name Link
🔨 Latest commit 66ff363
🔍 Latest deploy log https://app.netlify.com/projects/circuitverse/deploys/684ec6b34870bb0007d7e004
😎 Deploy Preview https://deploy-preview-601--circuitverse.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 47 (no change from production)
Accessibility: 72 (no change from production)
Best Practices: 92 (no change from production)
SEO: 80 (no change from production)
PWA: -
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (4)
src/simulator/src/i18n.ts (4)

3-5: Refine typing for window.locale.
Avoid casting window to any. Extend the global Window interface in a .d.ts file or inline to declare locale?: string. Then you can safely use window.locale ?? 'en' without any:

declare global {
  interface Window { locale?: string }
}
const userLocale = window.locale ?? 'en'

9-11: Rename finalFallback to fallbackLocale.
fallbackLocale is more descriptive than finalFallback. For clarity, update the constant name and its usages:

- const finalFallback = 'en'
+ const fallbackLocale = 'en'

12-16: Use JSON module imports instead of require.
Using require for JSON requires resolveJsonModule and esModuleInterop. Consider importing statically:

import enMessages from './i18n/en.json'

const messages: Record<string, any> = {
  [fallbackLocale]: enMessages,
}

This aligns with ES module semantics and improves bundler compatibility.


24-26: Annotate banana type and export.
Explicitly type the banana variable (const banana: Banana = new Banana()) and consider exporting its type to aid downstream consumers:

import Banana from 'banana-i18n'
export type { Banana }
const banana: Banana = new Banana()
// ...
export default banana
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8d8ca00 and 66ff363.

📒 Files selected for processing (2)
  • src/simulator/src/i18n.js (0 hunks)
  • src/simulator/src/i18n.ts (1 hunks)
💤 Files with no reviewable changes (1)
  • src/simulator/src/i18n.js
🔇 Additional comments (2)
src/simulator/src/i18n.ts (2)

1-2: Verify default import from banana-i18n.
The code uses a default import; ensure the library’s typings support import Banana from 'banana-i18n' and that esModuleInterop/allowSyntheticDefaultImports are correctly configured.


6-8: Review load order: setLocale before load.
You call banana.setLocale(userLocale) before loading any messages. Verify that the library handles this order correctly or consider moving setLocale after banana.load(messages) to ensure translations are registered before the locale is applied.

Comment on lines +17 to +23
// Try to load user's locale file
try {
messages[locale] = require(`./i18n/${locale}.json`)
} catch (err) {
console.warn(`Could not load locale file for ${locale}, falling back to ${finalFallback}.`)
}

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Set fallback locale on load failure.
If loading the user locale fails, banana.locale remains the unavailable locale. Reset it to the fallback to avoid missing translations at runtime:

try {
  messages[locale] = require(`./i18n/${locale}.json`)
} catch (err) {
  console.warn(`Could not load locale file for ${locale}, falling back to ${fallbackLocale}.`)
+ banana.setLocale(fallbackLocale)
}

Committable suggestion skipped: line range outside the PR's diff.

🤖 Prompt for AI Agents
In src/simulator/src/i18n.ts around lines 17 to 23, when loading the user's
locale file fails, the code only logs a warning but does not reset the locale to
the fallback. Modify the catch block to set banana.locale to finalFallback after
logging the warning, ensuring the application uses the fallback locale and
avoids missing translations at runtime.

@blazethunderstorm
Copy link
Author

@Arnabdaz @niladrix719 pls review the pr , thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Typescript Integration in /simulator/src files
1 participant