Fix initial automation config

[bramkragten]

Proposed change

Initial config was not updates for new automations, causing duplicate keys

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New feature (thank you!)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Example configuration

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue or discussion:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• There is no commented out code in this PR.
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

Summary by CodeRabbit

• New Features
  • Updated property names for automation configurations to improve clarity:
    • trigger is now triggers
    • condition is now conditions
    • action is now actions

[coderabbitai]

📝 Walkthrough

Walkthrough

The changes involve renaming three properties in the baseConfig object of the HaAutomationEditor class. The properties trigger, condition, and action have been updated to triggers, conditions, and actions, respectively. This modification reflects a shift in naming convention for these properties.

Changes

File Path	Change Summary
src/panels/config/automation/ha-automation-editor.ts	Property names updated: trigger → triggers, condition → conditions, action → actions

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 305cecb and c02b62b.

📒 Files selected for processing (1)

• src/panels/config/automation/ha-automation-editor.ts (1 hunks)

🔇 Additional comments not posted (3)

src/panels/config/automation/ha-automation-editor.ts (3)

Line range hint 1-1000: Summary of changes and potential impact

The main change in this file is the update of property names from singular to plural form (trigger → triggers, condition → conditions, action → actions) in the baseConfig object. This change improves clarity and consistency in the code.

While this change is beneficial, it's important to consider its potential impact:

1. Ensure that all references to these properties within this file and across the codebase are updated accordingly.
2. Check if there are any external dependencies or APIs that might be affected by this change.
3. Update any relevant documentation or comments that reference these properties.
4. Consider adding a migration step if this change affects existing user configurations.

Overall, this is a positive change that improves code readability and consistency. However, due to its potentially wide-reaching effects, thorough testing and careful deployment are recommended.

---

Line range hint 1-1000: Ensure consistency throughout the file

While the change to plural form for triggers, conditions, and actions is a good improvement, it's crucial to ensure this change is applied consistently throughout the entire file.

To verify this, please run the following script to check for any remaining instances of the singular form in this file:

#!/bin/bash
# Search for any remaining usage of singular form in this file
echo "Searching for singular form usage in ha-automation-editor.ts:"
rg --type typescript "\b(trigger|condition|action)s?\b" src/panels/config/automation/ha-automation-editor.ts

If any inconsistencies are found, please update them to maintain uniformity across the codebase.

---

468-470: Update property names to plural form

The property names in the baseConfig object have been updated from singular to plural form:

• trigger → triggers
• condition → conditions
• action → actions

This change improves consistency and clarity, as these properties typically contain arrays of multiple triggers, conditions, and actions.

However, to ensure this change doesn't introduce any breaking changes or inconsistencies elsewhere in the codebase, let's verify the usage of these properties.

---

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 or @coderabbitai title 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.