Allow defining id for descriptor decorators #1724
Merged
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
This is necessary to allow non-miot integrations to use custom naming for their descriptors. It is undecided how these are to be exposed to downstreams in the end, but one example would be allowing defining light:brightness for light brightness across the board.
|
Ping @starkillerOG just that you are in the loop, too :-) This is related to allow defining standardized naming for common actions & properties used by "specialized" homeassistant platforms, e.g., |
rytilahti
added a commit
that referenced
this pull request
Feb 11, 2023
Follow the new standard set in #1724 Co-authored-by: Teemu R. <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is necessary to allow non-miot integrations to use custom naming for their descriptors. It is undecided how the standardized properties and actions are to be exposed to downstreams in the end, but one example would be allowing defining light:brightness for light brightness across the board.