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: libs/state/docs/concepts-and-best-practices.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,7 @@ Good:
28
28
In a first step you want to setup the state interface. A property that should change the view of your component should find its place in the interface.
29
29
View bindings and triggers, which in turn mutate your state, should be `Subjects`.
30
30
In the best case, you keep your state _normalized_.
// Reuse custom operations result for multiple subscribers and reemit the last calculated value.
34
+
// Reuse custom operations result for multiple subscribers and re-emit the last calculated value.
35
35
shareReplay({ bufferSize: 1, refCount: true })
36
36
);
37
37
```
38
38
39
-
Using the `stateful` operator gives you the advantage to insert custom logic to derive state without having to think about sharing or replaying. It will also apply `distinctUntilChanged` by default. But you can provide custom logic for distinct values aswell.
39
+
Using the `stateful` operator gives you the advantage to insert custom logic to derive state without having to think about sharing or replaying. It will also apply `distinctUntilChanged` by default. But you can provide custom logic for distinct values as well.
0 commit comments