Skip to content

Commit

Permalink
(docs): fixed small errors (#636)
Browse files Browse the repository at this point in the history
  • Loading branch information
0xflotus authored Jun 25, 2020
1 parent ce25ffa commit bcecb54
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -1407,7 +1407,7 @@ const [mutate] = useMutation(addTodo, {
})
```
The promise returned by `mutate()` can be helpful as well for performing more granualar control flow in your app, and if you prefer that that promise only resolves **after** the `onSuccess` or `onSettled` callbacks, you can return a promise in either!:
The promise returned by `mutate()` can be helpful as well for performing more granular control flow in your app, and if you prefer that that promise only resolves **after** the `onSuccess` or `onSettled` callbacks, you can return a promise in either!:
```js
const [mutate] = useMutation(addTodo, {
Expand Down Expand Up @@ -1831,7 +1831,7 @@ const queryInfo = useQuery({
- `status: String`
- Will be:
- `idle` if the query is idle. This only happens if a query is initialized with `enabled: false` and no inital data is available.
- `idle` if the query is idle. This only happens if a query is initialized with `enabled: false` and no initial data is available.
- `loading` if the query is in a "hard" loading state. This means there is no cached data and the query is currently fetching, eg `isFetching === true`
- `error` if the query attempt resulted in an error. The corresponding `error` property has the error received from the attempted fetch
- `success` if the query has received a response with no errors and is ready to display its data. The corresponding `data` property on the query is the data received from the successful fetch or if the query is in `manual` mode and has not been fetched yet `data` is the first `initialData` supplied to the query on initialization.
Expand Down

0 comments on commit bcecb54

Please sign in to comment.