The idea behind Canary is to extend the functionality of Lovelace in a non-drastic way. This is done mainly, by adding extra configuration options (extensions) to pre-existing Lovelace elements.
This plugin could be thought of as almost a staging ground for features that if suitable could end up in core Lovelace, hence the name borrowed from Chrome Canary. It's unclear how well that statement will hold, it could also be called "Extensions".
Much like card-mod Canary extends the default lovelace cards, so you don't need to actually define a canary-card for these options to work. The options are added to their respective cards as 'extensions'.
For more information head over to the wiki.
I'd like to recognise Thomas Lovén's influence on this card, his work on card-tools made the creation of this vastly quicker and easier. Reference to his and other people's lovelace cards is, at this point, like 90% of my knowledge on JavaScript and polymer UI. Code from Thomas Lovén's card-mod is the backbone of the extensions to lovelace and what gave me this idea in the first place.
resources:
- url: /hacsfiles/lovelace-canary/canary.js
type: module
![@renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=64&v=4){kind=small}
