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: docs/api/createSlice.mdx
+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
@@ -359,7 +359,7 @@ reducers: (create) => {
359
359
360
360
### `extraReducers`
361
361
362
-
Conceptually, each slice reducer "owns" its slice of state. There's also a natural correspondance between the update logic defined inside `reducers`, and the action types that are generated based on those.
362
+
Conceptually, each slice reducer "owns" its slice of state. There's also a natural correspondence between the update logic defined inside `reducers`, and the action types that are generated based on those.
363
363
364
364
However, there are many times that a Redux slice may also need to update its own state in response to action types that were defined elsewhere in the application (such as clearing many different kinds of data when a "user logged out" action is dispatched). This can include action types defined by another `createSlice` call, actions generated by a `createAsyncThunk`, RTK Query endpoint matchers, or any other action. In addition, one of the key concepts of Redux is that many slice reducers can independently respond to the same action type.
Copy file name to clipboardExpand all lines: docs/rtk-query/api/created-api/hooks.mdx
+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
@@ -370,7 +370,7 @@ selectFromResult: () => ({})
370
370
- `trigger`: A function that triggers an update to the data based on the provided argument. The trigger function returns a promise with the properties shown above that may be used to handle the behavior of the promise
371
371
- `mutationState`: A query status object containing the current loading state and metadata about the request, or the values returned by the `selectFromResult` option where applicable.
372
372
Additionally, this object will contain
373
-
- a `reset` method to reset the hook back to it's original state and remove the current result from the cache
373
+
- a `reset` method to reset the hook back to its original state and remove the current result from the cache
374
374
- an `originalArgs` property that contains the argument passed to the last call of the `trigger` function.
375
375
376
376
#### Description
@@ -460,7 +460,7 @@ type UseQuerySubscriptionResult = {
460
460
461
461
- `arg`: The argument passed to the query defined in the endpoint.
462
462
You can also pass in `skipToken` here as an alternative way of skipping the query, see [skipToken](#skiptoken)
463
-
- `options`: A set of options that control the fetching behaviour of the hook
463
+
- `options`: A set of options that control the fetching behavior of the hook
464
464
465
465
- **Returns**
466
466
- An object containing a function to `refetch` the data
0 commit comments