Fix french maintenance translation (inverted entries)

[mcarbonne]

What type of PR is this?

• bug

What this PR does / why we need it:

Fixed inverted translation entries.

Summary by CodeRabbit

• New Features
  • Updated French localization for error messages related to maintenance operations.
  • Improved clarity in user feedback with corrected messages for creation and deletion errors.

[coderabbitai]

Walkthrough

The pull request involves updates to the French localization file for a frontend application, specifically correcting error messages related to maintenance operations. The changes include adjustments to the toast messages for failed creation and deletion actions, ensuring that the messages accurately reflect the operations being performed. The overall structure of the localization file remains unchanged, with no new keys added or removed.

Changes

File	Change Summary
frontend/locales/fr.json	Updated toast messages in the "maintenance" section: - failed_to_create: changed from "Échec de suppression de l'entrée" to "Échec de création de l'entrée". - failed_to_delete: changed from "Échec de création de l'entrée" to "Échec de suppression de l'entrée".

Possibly related PRs

• In maintenance view, change link to aim maintenance page of item #270: The changes in this PR involve the maintenance view, which is relevant to the context of the localization updates in the main PR, as both pertain to improving user interactions during maintenance operations. However, there are no direct code changes in common between the two PRs.

Security Recommendations

• Ensure that any localization files are properly sanitized to prevent injection attacks, particularly if user-generated content is involved. Regularly review and update localization files to maintain clarity and security.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between b5c7566 and 85d62d8.

📒 Files selected for processing (1)

• frontend/locales/fr.json (1 hunks)

🔇 Additional comments (2)

frontend/locales/fr.json (2)

Line range hint 1-999: Security Review: No security concerns identified

✅ The translation changes:

• Contain only plain text without HTML/JavaScript
• Don't include any sensitive information
• Don't introduce any XSS vectors

---

202-203: LGTM! Translation fixes correctly address the inverted messages.

The changes properly fix the inverted translations:

• "failed_to_create" now correctly shows "Échec de création de l'entrée" (Creation failure)
• "failed_to_delete" now correctly shows "Échec de suppression de l'entrée" (Deletion failure)

Let's verify the translations are consistent with other language files:

✅ Verification successful

French translations are now correctly aligned with other language files

The verification confirms that the French translations for "failed_to_create" and "failed_to_delete" are now semantically consistent with all other language files in the repository:

• All languages follow the pattern of "Failed to create" and "Failed to delete" in their respective translations
• The French translations now properly match this semantic structure, fixing the previous inversion

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check if other language files have consistent translations for these keys
# This helps ensure the French translations align with other languages

# Search for failed_to_create and failed_to_delete keys in all locale files
echo "Checking translations in other language files..."
fd -e json . frontend/locales -x jq -r '.maintenance.toast | select(.failed_to_create != null or .failed_to_delete != null) | {file: input_filename, create: .failed_to_create, delete: .failed_to_delete}'

Length of output: 2318

---

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 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.