Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/exercise/02.md
Original file line number Diff line number Diff line change
Expand Up @@ -96,7 +96,7 @@ Unfortunately, the ESLint plugin is unable to determine whether the
and normally I'd say just ignore it and move on. But, there's another solution
to this problem which I think is probably better.

Instead, of accepting `dependencies` to `useAsync`, why don't we just treat the
Instead of accepting `dependencies` to `useAsync`, why don't we just treat the
`asyncCallback` as a dependency? Any time `asyncCallback` changes, we know that
we should call it again. The problem is that because our `asyncCallback` depends
on the `pokemonName` which comes from props, it has to be defined within the
Expand Down