-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Additional views based on labels; updated sorting of areas #141
Open
mtinner
wants to merge
18
commits into
AalianKhan:main
Choose a base branch
from
mtinner:main
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
…and then by name.
Feature/label extended views
label based icon
Feature/label extended views
enable label based areas
fix title for subview card if there are more than one entry per label
mtinner
changed the title
Extend views by labels; updated sorting of areas
Additional views based on labels; updated sorting of areas
May 28, 2024
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.
Update order for areas according to following priority
Split domain views
Since entities of different types belong to the same domain in home assistant, this can be a risk for the user.
E.g. window and shutters belongs both to the domain "cover". If I want to open all my shutters by a simple click, for example to prevent damage during a storm, I do not want to open my windows as well.
So in my opinion, users would have a huge benefit, if they can split them into separate views. User can reach this by add the entity to a label with a predefined prefix ms_domain_{{groupName}} (e.g. ms_cover_windows).
To make sure the controls still fits, the label name has to contain the correct same domain as its entry.
The {{groupName}} and the optional given icon in the label will be reused in the tab, navigation and as a name on the view.
Labeled entities are no longer grouped in the "default" view.
This solved this issue as well: #107
Order views incl. extra_views
Not only is it possible to order the new label-based views, but it is now also possible to set an order for extra_views. Solves #61, #139, #142
illustation.webm