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
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ Further, avoiding complexity like two-way data bindings, or the spaghetti engend
23
23
24
24
## Support for Legacy Platforms
25
25
26
-
`ImmutableData-Legacy` is a subset of the functionality in our original `ImmutableData` project. To support legacy platforms, we made some changes. Some of these changes — like migrating from `Observable` to `Combine` when notifying components that Selector Outputs have changed — are implementation details that should not affect how product engineers build components. The biggest change to our *interface* — the `public` API that product engineers need — is that Selectors only accept single Dependency Selectors. We do not support variadic types and parameter packs in this version of our infra.
26
+
`ImmutableData-Legacy` is a subset of the functionality in our original `ImmutableData` project. Some of the changes — like migrating from `Observable` to `Combine` when notifying components that Selector Outputs have changed — are implementation details that should not affect how product engineers build components. The biggest change to our *interface* — the `public` API that product engineers need — is that Selectors only accept single Dependency Selectors. We do not support variadic types in this version of our infra.
0 commit comments