Unify Areas and area-detail section headers - #32
Merged
Conversation
Introduce a shared Mortar SectionHeader component and render the Areas grid through SectionGrid so section-header styling and spacing match the area-detail grid by construction. - Add Mortar SectionHeader (owns its own vertical spacing; isFirst suppresses the leading gap) - Refactor AreasView onto SectionGrid/TileGridEngine (areas as .medium tiles; 2-up compact / 3-up regular), enabling future reordering - Align AreaDetailView section spacing onto the shared component - Document the /** */ multi-line comment convention in swift-style.md Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
adborbas
force-pushed
the
unify-section-headers
branch
from
July 17, 2026 18:04
64bf4e6 to
4745ad8
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Changes
SectionHeadercomponent that owns its own vertical spacing (isFirstsuppresses the leading gap for the first section).HomeView) to render throughSectionGrid/TileGridEngine— areas become.mediumtiles (2-up in compact width, 3-up in regular). This makes header spacing match the area-detail grid by construction and lays the groundwork for reordering (isEditing/onReorderwired but dormant).AreaDetailViewsection spacing onto the shared component./** */multi-line comment convention in.claude/rules/swift-style.md.Why
The Areas tab (floor grouping) and area-detail (entity categories) previously used two different, inconsistent section headers (
.title3.bold()with ad-hoc padding vs.headline). They now share one component with identical font and spacing, verified within ≤3 pt across both screens.Notes