jeans/developers.home-assistant
jeans/developers.home-assistant
1
0
Fork 0
mirror of https://github.com/home-assistant/developers.home-assistant.git synced 2025-07-19 15:26:29 +00:00
Code Issues Packages Projects Releases Wiki Activity

Remove wrong information from blog post (#1222)

Browse Source 
Co-authored-by: Zack Barett <arnett.zackary@gmail.com>
This commit is contained in:
Bram Kragten 2022-02-22 14:26:11 +01:00 committed by GitHub
parent 97666fc85d
commit c10a33b040
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
blog/2022-02-18-paper-elements.md
View File

@ -14,5 +14,8 @@ We are converting our codebase from the deprecated `paper` elements to the new [
## What should custom cards do? ## What should custom cards do?
Custom Card Creators should bundle the components they rely on. This way they can control the version that is being used. The MWC components support registering their elements with custom names so they don't conflict with the Home Assistant frontend: [example from ESP Web Tools](https://github.com/esphome/esp-web-tools/blob/main/src/components/ewt-checkbox.ts) You can replace your `paper` elements with `mwc` elements but there is no gaurentee that these elements will be loaded when your users load your editor or cards, like it also was not guaranteed for `paper` elements. We can also not guarentee that we will use these elements forever, and an update of these elements could include breaking changes. We can not support this use case.
Our advise is to bundle your own elements, that don't collide with the elements Home Assistant uses.
See [this old blog post](https://developers.home-assistant.io/blog/2020/10/02/lazyMoreInfo#what-about-external-elements) for more information.