Skip to content

docs: minor improvements #1215

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 2, 2025
Merged

docs: minor improvements #1215

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 2 additions & 2 deletions ...eslint-plugin-react-hooks-extra/src/rules/no-direct-set-state-in-use-effect.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,7 +54,7 @@ const fullName = firstName + " " + lastName;

The rule **does not flag** indirect calls, such as:

- Inside `event` handlers.
- Inside event handlers.
- Inside `async` functions.
- Inside `setTimeout`, `setInterval`, `Promise.then`, etc.

Expand Down Expand Up @@ -151,7 +151,7 @@ export default function RemoteContent() {
If you need to fetch remote data within the component, consider using libraries like [TanStack Query](https://tanstack.com/query/v3/) or [SWR](https://swr.vercel.app/). They handle caching, re-fetching, and state management for you, making your code cleaner and more efficient.
</Callout>

The following examples are derived from the [React documentation](https://react.dev/learn/you-might-not-need-an-effect):
The following examples are derived from the [React Docs: You Might Not Need an Effect](https://react.dev/learn/you-might-not-need-an-effect):

### Failing

Expand Down