Use sections grid layout for view strategy #765
Merged
Conversation
This file contains hidden or 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
github-actions
bot
added
enhancement
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #765 +/- ##
==========================================
- Coverage 93.17% 93.14% -0.03%
==========================================
Files 29 29
Lines 2359 2350 -9
Branches 77 75 -2
==========================================
- Hits 2198 2189 -9
Misses 161 161
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
raman325
force-pushed
the
feature/view-strategy-sections-grid
branch
2 times, most recently
from
561cd09 to
531324b
Compare
Create section strategies that generate cards when HA resolves the view, allowing deferred data fetching and supporting both new lcm-slot cards and legacy entities cards via the use_slot_cards option. - Add LockCodeManagerSlotSectionStrategy for slot sections - Add LockCodeManagerLockSectionStrategy for lock codes sections - Simplify generateView to return strategy configs instead of cards - Remove unused entities parameter from generateView - Remove unused hass parameter from getSlotMapping Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
raman325
force-pushed
the
feature/view-strategy-sections-grid
branch
from
531324b to
259729e
Compare
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.
Proposed change
Change the view strategy from flat masonry layout to sections-based grid. Each card is now wrapped in its own section with
type: "grid", enabling a responsive grid pattern in Home Assistant's dashboard.Changes:
LovelaceSectionConfiginterface to type stubsgenerateViewto wrap each card in a section withtype: "grid"type: "sections"instead of default masonry layoutType of change
Additional information
🤖 Generated with Claude Code