Fix demo map panel

[bramkragten]

Proposed change

Fixes the demo map panel and migrates it to the new lovelace strategy panel.

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

  • Introduced mapping functionality for zone and person entities.
  • Enhanced Lovelace configuration to support a "map" URL path with specialized entities and strategy.

• Bug Fixes

  • Corrected the component_name and config properties in demo panels to ensure proper component rendering.

[coderabbitai]

Walkthrough

Walkthrough

This update introduces a new function mapEntities in entities.ts for mapping entities. It modifies mockLovelace in lovelace.ts to conditionally incorporate these entities when the url_path is "map." The demo_panels.ts file has been updated to rename the component_name from "map" to "lovelace" and adjust the config property.

Changes

File	Summary
demo/src/stubs/entities.ts	Added new mapEntities function to map zone and person entities with specific attributes.
demo/src/stubs/lovelace.ts	Updated mockLovelace function to conditionally add entities from mapEntities and return a strategy object if url_path is "map."
src/fake_data/demo_panels.ts	Modified component_name from "map" to "lovelace" and updated the config property from null to { mode: "storage" } in the demoPanels export.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant MockLovelaceFunction
    participant EntitiesModule
    participant LovelaceConfigHandler

    Client->>MockLovelaceFunction: Request lovelace/config with url_path
    alt url_path is "map"
        MockLovelaceFunction->>EntitiesModule: Call mapEntities()
        EntitiesModule-->>MockLovelaceFunction: Return entities
        MockLovelaceFunction->>Client: Return strategy { type: "map" }
    else url_path is not "map"
        MockLovelaceFunction->>LovelaceConfigHandler: Resolve configuration and localization
        LovelaceConfigHandler-->>MockLovelaceFunction: Return lovelace config
        MockLovelaceFunction->>Client: Return resolved config
    end

Loading

Tip

AI model upgrade

gpt-4o model for reviews and chat is now live

OpenAI claims that this model is better at understanding and generating code than the previous models. Please join our Discord Community to provide any feedback or to report any issues.

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE

Commits

Files that changed from the base of the PR and between 57e48e2 and 77cdd8a.

Files selected for processing (3)

• demo/src/stubs/entities.ts (1 hunks)
• demo/src/stubs/lovelace.ts (1 hunks)
• src/fake_data/demo_panels.ts (1 hunks)

Additional comments not posted (4)

demo/src/stubs/lovelace.ts (2)

10-10: Ensure mapEntities is correctly imported.

The import statement for mapEntities is correct and necessary for the new functionality.

---

16-24: Verify the new conditional block for url_path === "map".

The new conditional block correctly checks the url_path parameter and adds entities from mapEntities(). Ensure that mapEntities returns the expected entities and that the strategy object is correctly structured.

src/fake_data/demo_panels.ts (1)

69-72: Verify the consistency of component_name and config updates.

The component_name has been changed to "lovelace" and the config property has been updated to { mode: "storage" }. Ensure these changes are consistent with the rest of the configuration and that the new component_name and config are correctly handled in the application.

demo/src/stubs/entities.ts (1)

3-51: Ensure the correctness of mapEntities implementation.

The function mapEntities correctly maps zone and person entities, structuring their attributes. Ensure that the attributes are correctly structured and that the function integrates well with the rest of the application.

---

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.