Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Error if nesting under horizontal-stack
See original GitHub issueWhen I nest type: custom:mini-graph-card under the type: horizontal-stack I get an error:
Cannot read property ‘states’ of undefined
Is it a problem with this component or HA 0.81 version?
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Nesting vertical-stack inside horizontal-stack, can't solve ...
I'm trying to nest 3 veritcal stacks inside a horizontal stack so that I can get a 3 column layout for one of...
Read more >Trouble with nested matrices
Could you show me how to resize the entire matrix so that it is 90% of its size? It is now too wide...
Read more >Nested ListViews in flutter gives horizontal viewport error
In this case, a horizontal viewport was given an unlimited amount of I/flutter ( 9048): vertical space in which to expand.
Read more >Auto Layout Guide: Stack Views
This recipe shows a complex layout built from multiple layers of nested stack views. However, in this example, the stack views cannot create ......
Read more >Fix Stack View Disasters - Make App Pie
The stack view guesses at attributes and is often wrong. Change to horizontal. Change the Alignment to Fill and Distribution to Fill Equally....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Updated to 0.81.1 but still seeing this error. Will wait for 0.81.2. Thanks for info about the bug.
Should be fixed in v0.0.7, closing this.