Use context instead of stateObj for card features #25577
Merged
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.
Proposed change
Use
context
instead ofstateObj
for card features. It was already used in the editor and will open the possibility to have card features for other type of card (e.g. area card by passing anarea_id
)All the HA card features has been migrated in this PR.
Custom card features needs to migrate to this new API :
supported: (stateObj) => boolean
is replaced byisSupported: (hass, context) = boolean
context
property is set to card features instead ofstateObj
However, a backward compatibility has been added to avoid breaking change. A blog post will be written and the dev documentation will be updated.
Type of change
Example configuration
Additional information
Checklist
If user exposed functionality or configuration variables are added/changed: