🌐 New Crowdin updates

[lukevella]

Summary by CodeRabbit

• Localization
  • Added Russian translation for email-related error message.
  • Updated Russian email change request localization with expiration notice.
  • Added Spanish translation for email-related error message.
  • Updated Spanish email change request localization with expiration notice.
  • Added Dutch translation for email-related error message.
  • Updated Dutch email change request localization with expiration notice.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

2 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
app	⬜️ Ignored (Inspect)	Visit Preview		Jan 16, 2025 6:44pm
landing	⬜️ Skipped (Inspect)			Jan 16, 2025 6:44pm

[coderabbitai]

Walkthrough

This pull request introduces localization updates across multiple languages, specifically Russian, Spanish, and Dutch, by adding new string entries to handle email-related errors and provide clarity in email communications. It includes messages informing users when an email address is already in use and details regarding the expiration of email verification links. These changes enhance user experience during account creation and email change processes.

Changes

File	Change Summary
apps/web/public/locales/ru/app.json	Added emailAlreadyInUse error message for email address conflict
packages/emails/locales/ru/emails.json	Added changeEmailRequest_text3 explaining link expiration in email change request
apps/web/public/locales/es/app.json	Added emailAlreadyInUse error message for email address conflict
packages/emails/locales/es/emails.json	Added changeEmailRequest_text3 explaining link expiration in email change request
apps/web/public/locales/nl/app.json	Added emailAlreadyInUse error message for email address conflict
packages/emails/locales/nl/emails.json	Added changeEmailRequest_text3 explaining link expiration in email change request

Possibly related PRs

• 🌐 New Crowdin updates #1103: This PR adds new string entries related to email management, including the "emailAlreadyInUse" key, which is directly related to the changes made in the main PR.
• 🌐 New Crowdin updates #1115: This PR includes updates to the Hungarian localization file that also involve the "emailAlreadyInUse" key, indicating a similar context of email-related error messages.
• 🌐 New Crowdin updates #1494: This PR introduces new entries for email change notifications, including the "emailAlreadyInUse" key, which aligns with the main PR's focus on email-related error handling.

Poem

🐰 In the fields where emails play,
New strings hop in bright array.
"Already in use," they softly say,
Helping users find their way.
With links that tick, and time that flies,
Clarity blooms, oh how it ties! 🌼

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 58ed487 and a6b8fad.

📒 Files selected for processing (2)

• apps/web/public/locales/es/app.json (1 hunks)
• packages/emails/locales/es/emails.json (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (2)

• apps/web/public/locales/es/app.json
• packages/emails/locales/es/emails.json

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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. (Beta)
• @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.