Update State semantics to match new Xcode 27 SwiftUI
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 330
- Forks
- 76
- Avg merge
- 3h 6m
- Merged PRs (30d)
- 1
Description
https://developer.apple.com/documentation/updates/swiftui
June 2026
General
Build your project in Xcode 27 or later so that the
@Stateattribute uses the State() macro to create a state value in an App, Scene, or View. This change only initializes and stores your property once when it’s a class.
@State is now a macro instead of a @propertyWrapper.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked SwiftUI update and the State macro and property-wrapper references, then locate skip-ui's State implementation and its App, Scene, and View entry points. Done means State follows the Xcode 27 semantics for class-backed properties and remains consistent across those SwiftUI contexts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- mobile-dev
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100