Update french translation

[Crae]

Correct a misspelling in the french translation.
Add the missing translation key for french language.

Summary by CodeRabbit

• Bug Fixes

  • Corrected a typo in the French translation for the battery charge level sensor.

• New Features

  • Introduced additional French translation entries for vehicle monitoring alerts and parameters such as brake fluid level, service scheduling, engine coolant level, oil level, internal vehicle identification, latest health data update, and software version release.

[coderabbitai]

Walkthrough

The pull request updates the French translation file for the Polestar API. It corrects a typo in the battery charge level sensor label, changing "betterie" to "batterie". Additionally, it adds nine new translation keys for parameters such as brake fluid level warning, service reminders, oil level warning, and others, expanding the available monitored alerts.

Changes

File	Change Summary
custom_components/.../fr.json	Corrects typo for polestar_battery_charge_level; adds translations for nine new Polestar API entities including brake fluid, service reminders, and warnings.

Possibly related PRs

• Update fr.json #318: Addresses the same typo correction in the French translation file, directly linking the changes.

Poem

I'm a little rabbit, hopping with glee,
Tweaking translations for all to see.
Corrected a typo, added alerts galore,
With French finesse, we now have more.
Hop along, celebrate—let's explore! 🐇

---

📜 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 8a795ce and 71d2704.

📒 Files selected for processing (1)

• custom_components/polestar_api/translations/fr.json (3 hunks)

🔇 Additional comments (10)

custom_components/polestar_api/translations/fr.json (10)

51-53: Corrected Spelling in Battery Translation
The translation for "polestar_battery_charge_level" now correctly spells "batterie" instead of the previous "betterie". This correction improves clarity and professionalism in the UI.

---

54-56: Added Brake Fluid Level Warning Translation
The new key "polestar_brake_fluid_level_warning" with the value "Alerte de niveau de liquide de frein" has been added. This addition expands the monitoring capabilities and uses correct technical terminology.

---

78-80: Added Days to Service Translation
The newly introduced key "polestar_days_to_service" with the value "Jours jusqu'au prochain service" is implemented correctly to support service-related alerts.

---

81-83: Added Distance to Service Translation
The key "polestar_distance_to_service" is added with the translation "Distance jusqu'au prochain service", providing clear information for upcoming service intervals.

---

84-86: Added Engine Coolant Level Warning Translation
The new translation key "polestar_engine_coolant_level_warning" with the value "Alerte de niveau de liquide de refroidissement moteur" is a welcome addition for monitoring engine coolant levels.

---

102-104: Added Internal Vehicle ID Translation
Introducing "polestar_internal_vehicle_id" with the translation "Identifiant interne du véhicule" helps in clearly displaying the vehicle’s internal identifier.

---

108-110: Added Last Updated Health Data Translation
The key "polestar_last_updated_health_data" is added with "Dernière mise à jour des données de santé", ensuring consistency with other health data related keys.

---

117-119: Added Oil Level Warning Translation
The addition of "polestar_oil_level_warning" with the translated value "Alerte de niveau d'huile" aligns well with similar sensor alert keys.

---

123-125: Added Service Warning Translation
The new translation "polestar_service_warning" with the value "Alerte de service" is added to enhance the API’s alerting mechanism regarding service needs.

---

129-131: Added Software Version Release Date Translation
The translation key "polestar_software_version_release" now appears with "Date de la version du logiciel", clearly indicating the release date of the software version.

---

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.

[jschlyter]

Merci beaucoup!