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-09 18:36:29 +00:00
Code Issues Packages Projects Releases Wiki Activity

Create Blog Post on Paper Elements being removed (#1216)

Browse Source 
Co-authored-by: Paulus Schoutsen <balloob@gmail.com>
Co-authored-by: Franck Nijhof <git@frenck.dev>
This commit is contained in:
Zack Barett 2022-02-18 13:29:50 -06:00 committed by GitHub
parent 66a547f18b
commit 5c7f71620a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 18 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -0,0 +1,18 @@
---
author: Zack Barett
authorURL: https://github.com/zsarnett
title: "Paper Elements are being removed"
---
In the Home Assistant Core 2022.3 release, we are removing all of the `paper-dropdown-menu` and `paper-input` elements in the Frontend Repository. This means that any custom card that was previously using these elements in the card or card editor will no longer render correctly and will require updates to its codebase.
Custom Cards using the elements used in the Home Assistant Frontend have never been supported.
## Why did we do this?
We are converting our codebase from the deprecated `paper` elements to the new [Material Web Components](https://github.com/material-components/material-components-web-components) from Google. This is to keep our frontend up to date with the latest components and features.
## 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)