Skip to content

fix: fixed use-no-direct-set-state-in-use-effect deferred setState calls detection, closes #1117 #1119

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.

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

Conversation

Rel1cx
Copy link
Owner

@Rel1cx Rel1cx commented Jun 3, 2025

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Docs
  • Test
  • New Binding issue #___
  • Code style update
  • Refactor
  • Build-related changes
  • Other, please describe:

Does this PR introduce a breaking change?

  • Yes, and the changes were approved in issue #___
  • No

Checklist

  • When resolving issues, they are referenced in the PR's title (e.g fix: remove a typo, closes #___, #___)
  • I have added a convincing reason for adding this feature, if necessary

Other information

Copy link

vercel bot commented Jun 3, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
eslint-react ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 3, 2025 11:04am

@Rel1cx Rel1cx force-pushed the fix-use-no-direct-set-state-in-use-effect-deferred-set-state-call branch from a65df75 to d78790c Compare June 3, 2025 11:01
@Rel1cx Rel1cx merged commit c2bb0a2 into main Jun 3, 2025
9 checks passed
@Rel1cx Rel1cx deleted the fix-use-no-direct-set-state-in-use-effect-deferred-set-state-call branch June 3, 2025 11:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant