Treat default_view as view by default#6758
Conversation
|
@andrey-git, thanks for your PR! By analyzing the history of the files in this pull request, we identified @balloob, @pvizeli and @fabaff to be potential reviewers. |
|
I don't think that this is the right solution either. We should raise an error or else people might be confused on how to specify a view because there are two ways. We should also test this. |
|
I will add tests, but requiring |
|
Both approaches will be breaking changes. Because someone might want to have a group called I don't like auto-fixing config because it is a slippery slope. We start auto fixing more and more and all of a sudden we get into a situation where 2 auto-fixes collide and we have to start making a decision that can break things for some users… so better to never auto fix. |
|
So maybe make a fix in a different direction - make default_view without |
|
Isn't it already treated as a non-view group ? |
|
Instead this will run (despite the group not being a view): |
|
Good point! Yes, we should update those pieces of code. |
|
Created home-assistant/frontend#251 |
Description:
Treat default_view as view by default
Redo of home-assistant/home-assistant-js-websocket/pull/6
If the code does not interact with devices:
toxrun successfully. Your PR cannot be merged unless tests pass