This repository has been archived by the owner on Feb 22, 2021. It is now read-only.
Don't use utilities from home-assistant-polymer #65
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Starting Home Assistant 0.70 we're clearly defining the custom UI and custom panel API to make sure that we can guarantee that working in future releases.
One of the steps to make a more clear API is to not allow custom UI or panels to use our internal utilities (i'm going to write a blog post about this later).
Anyway, for now, it looks like ha-floorplan only used one utility function. Instead of referencing HAWS, I've inlined that function. This should make ha-floorplan work with 0.70.
We're going to deprecate HTML imports (also more about this later) and move to JavaScript imports. More info about this later too.