Fully updated for Xcode 11.4
SwiftUI uses the
@State property wrapper to allow us to modify values inside a struct, which would normally not be allowed because structs are value types. When we put
@State before a property, we effectively move its storage out from our struct and into shared storage managed by SwiftUI. This means SwiftUI can destroy and recreate our struct whenever needed (and this can happen a lot!), without losing the state it was storing.
@State should be used with simple struct types such as
Int, and generally shouldn’t be shared with other views. If you want to share values across views, you should probably use
@EnvironmentObject instead – both of those will ensure that all views will be refreshed when the data changes.
To re-enforce the local nature of
@State properties, Apple recommends you mark them as
private, like this:
@State private var username = ""
This isn’t required, but it seems like smart practice.
SPONSORED Catch bugs as soon as they happen and know exactly why a crash occurred by integrating Instabug's SDK in one minute. You will automatically receive device data, network logs, and reproduction steps with every bug and crash report.
Link copied to your pasteboard.