🐛 app: disable translations key separator

[dieguezguille]

Summary by CodeRabbit

• Chores
  • Updated localization initialization configuration formatting and explicit option settings for improved clarity and consistency.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[changeset-bot]

⚠️ No Changeset found

Latest commit: e11ab83

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[gemini-code-assist]

Summary of Changes

Hello @dieguezguille, I'm Gemini Code Assist¹! 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 addresses a bug related to how translation keys are interpreted within the application's internationalization setup. By disabling the key separator in the i18n configuration, the system will now correctly recognize translation keys as literal strings, resolving potential issues where keys containing periods or other separator characters might have been incorrectly parsed as nested objects. This ensures accurate retrieval of translated content.

Highlights

• Internationalization Configuration: The keySeparator option has been explicitly set to false within the i18n.init configuration in src/app/_layout.tsx. This change ensures that translation keys are treated as complete strings, preventing unintended parsing of keys containing separator characters.

Using Gemini Code Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

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

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[coderabbitai]

Walkthrough

The i18n initialization configuration in src/app/_layout.tsx has been reformatted from a single-line object to a multi-line structure with explicit keySeparator: false and nsSeparator: false options, while preserving existing fallbackLng and resources properties.

Changes

Cohort / File(s)	Summary
i18n Configuration src/app/_layout.tsx	Expanded i18next init() call to explicitly define separator options (keySeparator: false, nsSeparator: false) in multi-line format; no behavioral changes

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• 🐛 app fixes #652: Updates i18n initialization in the same file with separator configuration options (nsSeparator/keySeparator)

Suggested reviewers

• franm91

🚥 Pre-merge checks | ✅ 2

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: disabling the translations key separator in the i18n configuration by setting keySeparator: false.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch guille

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Code Review

This pull request correctly disables the keySeparator in the i18next configuration. This is necessary to support translation keys that contain dots, which are present in the Spanish translation file (es.json). The change also improves code readability by formatting the configuration object over multiple lines. The implementation is correct and addresses the underlying issue effectively.