Jorge Cabiedes 257b033fc7 [Compiler] Avoid capturing global setStates for no-derived-computations lint (#35135) ...

Summary:
This only matters when enableTreatSetIdentifiersAsStateSetters=true

This pattern is still bad. But Right now the validation can only
recommend to move stuff to "calculate in render"

A global setState should not be moved to render, not even conditionally
and you can't remove state without crossing Component boundaries, which
makes this a different kind of fix.

So while we are only suggesting "calculate in render" as a fix we should
disallow the lint from throwing in this case IMO

Test Plan:
Added a fixture

---
[//]: # (BEGIN SAPLING FOOTER)
Stack created with [Sapling](https://sapling-scm.com). Best reviewed
with [ReviewStack](https://reviewstack.dev/facebook/react/pull/35135).
* __->__ #35135
* #35134

2025-11-13 22:56:06 -08:00

..

babel-plugin-react-compiler

[Compiler] Avoid capturing global setStates for no-derived-computations lint (#35135)

2025-11-13 22:56:06 -08:00

eslint-plugin-react-compiler

[compiler] Cleanup and enable validateNoVoidUseMemo (#34882)

2025-10-16 13:08:57 -07:00

make-read-only-util

[compiler] Add missing copyrights (#33004)

2025-04-23 22:04:44 -04:00

react-compiler-healthcheck

[compiler] improve zod v3 backwards compat (#34877)

2025-10-16 09:46:55 -07:00

react-compiler-runtime

[compiler] Add missing copyrights (#33004)

2025-04-23 22:04:44 -04:00

react-forgive

[forgive] Various fixes to prepare for internal sync (#34928)

2025-10-21 10:57:18 -04:00

react-mcp-server

[compiler] improve zod v3 backwards compat (#34877)

2025-10-16 09:46:55 -07:00

snap

[compiler] improve zod v3 backwards compat (#34877)

2025-10-16 09:46:55 -07:00