Form and Section - #31
Merged
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
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.
Fifth tier, second half: grouped forms.
DatePickerremains deferred to its own tier.What's new
Form— a scrolling container of sections; the interpreter renders it as a vertically-scrolling column.Section—Section("Header"),Section(header:footer:), or unlabeled; rendered as an inset rounded group (surface variant) with an uppercase header, dividers between rows, and an optional footer.Rows are ordinary views, so toggles, sliders, text fields, and stacks work inside a section unchanged.
Verification
swift test— new test (Form nests a Section with its header and rows), 48 total passingDeferred
DatePicker(needs a date type + a Compose date dialog) — next tier. Section content here is string headers/footers; view-based headers are not modeled.