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: Sources/ComposableArchitecture/ViewStore.swift
+16-8Lines changed: 16 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -151,7 +151,8 @@ public final class ViewStore<ViewState, ViewAction>: ObservableObject {
151
151
@available(
152
152
iOS,
153
153
deprecated:9999.0,
154
-
message:"""
154
+
message:
155
+
"""
155
156
Use 'init(_:observe:removeDuplicates:)' to make state observation explicit.
156
157
157
158
When using ViewStore you should take care to observe only the pieces of state that your view needs to do its job, especially towards the root of the application. See the performance article for more details:
@@ -162,7 +163,8 @@ public final class ViewStore<ViewState, ViewAction>: ObservableObject {
162
163
@available(
163
164
macOS,
164
165
deprecated:9999.0,
165
-
message:"""
166
+
message:
167
+
"""
166
168
Use 'init(_:observe:removeDuplicates:)' to make state observation explicit.
167
169
168
170
When using ViewStore you should take care to observe only the pieces of state that your view needs to do its job, especially towards the root of the application. See the performance article for more details:
@@ -173,7 +175,8 @@ public final class ViewStore<ViewState, ViewAction>: ObservableObject {
173
175
@available(
174
176
tvOS,
175
177
deprecated:9999.0,
176
-
message:"""
178
+
message:
179
+
"""
177
180
Use 'init(_:observe:removeDuplicates:)' to make state observation explicit.
178
181
179
182
When using ViewStore you should take care to observe only the pieces of state that your view needs to do its job, especially towards the root of the application. See the performance article for more details:
@@ -184,7 +187,8 @@ public final class ViewStore<ViewState, ViewAction>: ObservableObject {
184
187
@available(
185
188
watchOS,
186
189
deprecated:9999.0,
187
-
message:"""
190
+
message:
191
+
"""
188
192
Use 'init(_:observe:removeDuplicates:)' to make state observation explicit.
189
193
190
194
When using ViewStore you should take care to observe only the pieces of state that your view needs to do its job, especially towards the root of the application. See the performance article for more details:
@@ -609,7 +613,8 @@ extension ViewStore where ViewState: Equatable {
609
613
@available(
610
614
iOS,
611
615
deprecated:9999.0,
612
-
message:"""
616
+
message:
617
+
"""
613
618
Use 'init(_:observe:)' to make state observation explicit.
614
619
615
620
When using ViewStore you should take care to observe only the pieces of state that your view needs to do its job, especially towards the root of the application. See the performance article for more details:
@@ -620,7 +625,8 @@ extension ViewStore where ViewState: Equatable {
620
625
@available(
621
626
macOS,
622
627
deprecated:9999.0,
623
-
message:"""
628
+
message:
629
+
"""
624
630
Use 'init(_:observe:)' to make state observation explicit.
625
631
626
632
When using ViewStore you should take care to observe only the pieces of state that your view needs to do its job, especially towards the root of the application. See the performance article for more details:
@@ -631,7 +637,8 @@ extension ViewStore where ViewState: Equatable {
631
637
@available(
632
638
tvOS,
633
639
deprecated:9999.0,
634
-
message:"""
640
+
message:
641
+
"""
635
642
Use 'init(_:observe:)' to make state observation explicit.
636
643
637
644
When using ViewStore you should take care to observe only the pieces of state that your view needs to do its job, especially towards the root of the application. See the performance article for more details:
@@ -642,7 +649,8 @@ extension ViewStore where ViewState: Equatable {
642
649
@available(
643
650
watchOS,
644
651
deprecated:9999.0,
645
-
message:"""
652
+
message:
653
+
"""
646
654
Use 'init(_:observe:)' to make state observation explicit.
647
655
648
656
When using ViewStore you should take care to observe only the pieces of state that your view needs to do its job, especially towards the root of the application. See the performance article for more details:
0 commit comments