Skip to content

StateObject anti-pattern info #21

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
lanserxt wants to merge 3 commits into
base: main
Choose a base branch
from
+3 −1
Open

StateObject anti-pattern info #21

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
9d2e297
Patter suggestion
Feb 8, 2026
3102825
Merge branch 'main' into main
lanserxt Feb 8, 2026
79a349f
More clear suggestion for Child Views
Feb 8, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion swiftui-expert-skill/references/state-management.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -151,7 +151,9 @@ struct GoodView: View {
```

### @StateObject instantiation in View's initializer
If you need to create a @StateObject with initialization parameters in your view's custom initializer, be aware of redundant allocations and hidden side effects.

This approach is an anti-pattern in general. Prefer storing the StateObject in the parent view or wherever the model is actually owned, then pass it down (use @ObservedObject, @EnvironmentObject, or @Bindable (for @Observable)) to keep ownership and lifecycle explicit.
If you need to create a @StateObject with initialization parameters in your view's custom initializer, be aware of redundant allocations and hidden side effects. Kudos to Vincent Pradeilles.

```swift
// WRONG - creates a new ViewModel instance each time the view's initializer is called
Expand Down