Skip to content

Commit 8e57358

Browse files
panckreousmarkerikson
authored andcommitted
remove "obviously" (#3418)
inspired by #2950 - I think using "obviously" here can be confusing by assuming a reader knows it's obvious (and why), vs just stating that it's the most common.
1 parent 86bca8c commit 8e57358

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/recipes/structuring-reducers/UpdatingNormalizedData.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -140,7 +140,7 @@ The example is a bit long, because it's showing how all the different slice redu
140140

141141
### Task-Based Updates
142142

143-
Since reducers are just functions, there's an infinite number of ways to split up this logic. While using slice reducers is obviously the most common, it's also possible to organize behavior in a more task-oriented structure. Because this will often involve more nested updates, you may want to use an immutable update utility library like [dot-prop-immutable](https://github.com/debitoor/dot-prop-immutable) or [object-path-immutable](https://github.com/mariocasciaro/object-path-immutable) to simplify the update statements. Here's an example of what that might look like:
143+
Since reducers are just functions, there's an infinite number of ways to split up this logic. While using slice reducers is the most common, it's also possible to organize behavior in a more task-oriented structure. Because this will often involve more nested updates, you may want to use an immutable update utility library like [dot-prop-immutable](https://github.com/debitoor/dot-prop-immutable) or [object-path-immutable](https://github.com/mariocasciaro/object-path-immutable) to simplify the update statements. Here's an example of what that might look like:
144144

145145
```js
146146
import posts from "./postsReducer";

0 commit comments

Comments
 (0)