Feat: Custom notification #1173
Draft
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
albinmedoc
reviewed
Feb 16, 2023
| styles: | ||
| card: | ||
| - overflow: > | ||
| [[[ | ||
| if (entity.state == "unavailable"){ | ||
| if (entity.state == "unavailable" || entity.state == variables.ulm_notification_state){ |
There was a problem hiding this comment.
This allow us to only specify notification based on the current entity.
There was a problem hiding this comment.
Nothing wrong with that but it would be great to make it more "open", allowing notification to be based on any entity.
|
What's the status of this PR, is there something I can help with? |
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.
No description provided.