Skip to content

Translations update from Hosted Weblate#932

Merged
frenck merged 1 commit intofrenck:mainfrom
weblate:weblate-spook-integration
Mar 26, 2025
Merged

Translations update from Hosted Weblate#932
frenck merged 1 commit intofrenck:mainfrom
weblate:weblate-spook-integration

Conversation

@weblate
Copy link
Copy Markdown
Contributor

@weblate weblate commented Mar 26, 2025

Translations update from Hosted Weblate for Spook/Integration.

Current translation status:

Weblate translation status

Currently translated at 38.4% (45 of 117 strings)

Translation: Spook/Integration
Translate-URL: https://hosted.weblate.org/projects/spook/integration/it/
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Mar 26, 2025

📝 Walkthrough

Walkthrough

The pull request updates the Italian translation file for the Spook component by adding several new entries. The changes expand both the entity section (including translations for buttons, sensors, events, and switches) and the issues section (with entries like user_issue and restart_required that include fix flow details). These modifications aim to enhance the localization of the component for Italian users.

Changes

File Path Change Summary
custom_components/spook/translations/it.json Updated Italian translations. Added new entity entries for buttons (homeassistant_reload, homeassistant_restart, repairs_ignore_all), sensors (e.g., homeassistant_area, homeassistant_automation, homeassistant_climate, etc.), event (repairs_event with state attributes), and switch (cloud_remote). Expanded issues section with user_issue (confirmation fix_flow) and restart_required (restart prompt).

Possibly related PRs

Suggested labels

maintenance

Poem

I'm a rabbit in a code burrow, hopping with delight,
Adding Italian words that shine so bright.
"Ricarica" and "Riavvia" lead the cheerful parade,
While "Ignora tutto" and sensors join the translation cascade.
Each line of text makes my heart do a leap,
Celebrating changes that make our component complete!


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.
    • 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.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai plan to trigger planning for file edits and PR creation.
  • @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.

@sonarqubecloud
Copy link
Copy Markdown

Copy link
Copy Markdown
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: 0

🧹 Nitpick comments (2)
custom_components/spook/translations/it.json (2)

142-151: User Issue Fix Flow Translation
The newly introduced "user_issue" entry under "issues" includes a "fix_flow" with a confirmation step that uses the placeholder {descrizione}. Please verify that the placeholder is correctly handled and substituted at runtime.


152-162: Restart Required Issue Translation
The "restart_required" entry provides both a clear title and an actionable fix flow step prompting a restart. The inclusion of the emoji 👻 adds a friendly tone; however, please review whether this stylistic choice is consistent with other translations and the overall brand voice.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between cac7e32 and 1b3b335.

📒 Files selected for processing (1)
  • custom_components/spook/translations/it.json (1 hunks)
🔇 Additional comments (5)
custom_components/spook/translations/it.json (5)

7-13: Config Restart Prompt Translations
The new entries under "choice_restart"—including "restart_later" with the translation "Riavvia più tardi", the existing "restart_now", and the descriptive prompt—provide clear guidance to users. Please verify that the tone and phrasing are consistent with the rest of the application’s UI.


20-30: Button Entity Translations
The additions for the button entities ("homeassistant_reload", "homeassistant_restart", and "repairs_ignore_all") are clear and align well with typical naming conventions. Ensure that these keys match exactly with their usage in the codebase to avoid key mismatches in the UI.


31-116: Sensor Entity Translations
A comprehensive set of translations has been added for various sensor entities. The Italian names such as "Aree", "Automazioni", "Climatizzatori", etc., appear consistent. It might be worth double-checking for potential pluralization or stylistic adjustments in Italian across similar keys—but overall, the implementation looks solid.


117-135: Event Entity Translations
The new "repairs_event" key with its nested "state_attributes" (covering "event_type", "domain", and "issue_id") is well structured and clearly translated. Confirm that these nested keys are correctly referenced within the system’s event handling logic.


136-140: Switch Entity Translation
The addition of "cloud_remote" with the translation "Telecomando" is straightforward and consistent with the UI terminology.

@frenck frenck added the maintenance Generic maintenance tasks. label Mar 26, 2025
@frenck frenck merged commit e7dad58 into frenck:main Mar 26, 2025
8 of 9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

maintenance Generic maintenance tasks.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants