You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -86,10 +86,10 @@ Just 2 steps to enable injection in your `SwiftUI` Views
86
86
87
87
> *Remember you **don't need** to remove this code when you are done, it's NO-OP in production builds.*
88
88
89
-
If you want to see your changes in action, you can enable an optional `Animation` variable on `Inject.animation` that will be used when ever new source code is injected into your application.
89
+
If you want to see your changes in action, you can enable an optional `Animation` variable on `InjectConfiguration.animation` that will be used when ever new source code is injected into your application.
Using `Inject` is demoed in this [example app](https://github.com/MarcoEidinger/InjectSwiftUIExample)
@@ -99,8 +99,8 @@ For standard imperative UI frameworks we need a way to clean-up state between co
99
99
100
100
I create the concept of **Hosts** that work really well in that context, there are 2:
101
101
102
-
-`Inject.ViewControllerHost`
103
-
-`Inject.ViewHost`
102
+
-`ViewControllerHost`
103
+
-`ViewHost`
104
104
105
105
How do we integrate this? We wrap the class we want to iterate on at the parent level, so we don’t modify the class we want to be injecting but we modify the parent callsite.
0 commit comments