Reload the card when changing the configuration in editor

[piitaya]

Proposed change

Cards need to be fully reloaded in preview mode

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 Statistic card preview broken #21340
• 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
  • Enhanced card functionality to rebuild when card type changes or if in preview mode.

[coderabbitai]

Walkthrough

Walkthrough

The update to the HuiCard class in hui-card.ts introduces a condition to rebuild the card if the card type changes or if the preview mode is enabled. This ensures the card is properly reconstructed to reflect any changes or the preview state.

Changes

File Path	Change Summary
src/panels/lovelace/cards/hui-card.ts	Updated the condition in the HuiCard class to rebuild the card when the type changes or when it is in preview mode.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant HuiCard
    participant CardElement

    User->>HuiCard: Set new elementConfig
    HuiCard->>HuiCard: Check if typeChanged or preview
    alt typeChanged or preview is true
        HuiCard->>HuiCard: Rebuild the card
    else
        HuiCard->>HuiCard: No action needed
    end

Loading

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE

Commits

Files that changed from the base of the PR and between 7edc4ef and 8536570.

Files selected for processing (1)

• src/panels/lovelace/cards/hui-card.ts (1 hunks)

Additional comments not posted (1)

src/panels/lovelace/cards/hui-card.ts (1)

153-156: Verify the correctness of the logic.

The changes ensure that the card rebuilds when the type changes or when in preview mode. This looks good and aligns with the PR objective.

However, ensure that all function calls to update handle the new logic correctly.

Verification successful

---

Verified the correctness of the logic.

The changes ensure that the card rebuilds when the type changes or when in preview mode. This aligns with the PR objective. The update method in src/panels/lovelace/cards/hui-card.ts is correctly handling the new logic.

• No issues found with the new logic in the update method.
• Other usages of update in different files do not impact this specific change.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify all function calls to `update` handle the new logic correctly.

# Test: Search for the method usage. Expect: Correct handling of the new logic.
rg --type typescript -A 5 $'update('

Length of output: 102

---

Script:

#!/bin/bash
# Description: Verify all function calls to `update` handle the new logic correctly.

# Test: Search for the method usage. Expect: Correct handling of the new logic.
rg --type typescript -A 5 'update\('

Length of output: 73

---

Script:

#!/bin/bash
# Description: Verify all function calls to `update` handle the new logic correctly.

# Test: Search for the method usage. Expect: Correct handling of the new logic.
rg -A 5 'update\('

Length of output: 19226

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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