[compiler] Fix false negatives and add data flow tree to compiler error for no-deriving-state-in-effects
#34995
+340
−67
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Oct 27, 2025
jorge-cab
force-pushed
the
pr34995
branch
4 times, most recently
from
4af24bf to
308f659
Compare
jorge-cab
changed the title
no-deriving-state-in-effectsno-deriving-state-in-effects
jorge-cab
force-pushed
the
pr34995
branch
2 times, most recently
from
6e29244 to
b762183
Compare
jorge-cab
force-pushed
the
pr34995
branch
2 times, most recently
from
1e2ab32 to
4a8789c
Compare
jorge-cab
commented
Oct 28, 2025
| This setState call is setting a derived value that depends on the following reactive sources: | ||
There was a problem hiding this comment.
Oh wait Prop: [props] missing here seems like a bug
…d instead update typeOfValue and fix infinite loops
Summary:
With this we are now comparing a snapshot of the derivationCache with the new changes every time we are done recording the derivations happening in the HIR.
We have to do this after recording everything since we still do some mutations on the cache when recording mutations.
Test Plan:
Test the following in playground:
```
// @validateNoDerivedComputationsInEffects_exp
function Component({ value }) {
const [checked, setChecked] = useState('');
useEffect(() => {
setChecked(value === '' ? [] : value.split(','));
}, [value]);
return (
<div>{checked}</div>
)
}
```
This no longer causes an infinite loop.
Added a test case in the next PR in the stack
…or for `no-deriving-state-in-effects` Summary: Revamped the derivationCache graph. This fixes a bunch of bugs where sometimes we fail to track from which props/state we derived values from. Also, it is more intuitive and allows us to easily implement a Data Flow Tree. We can print this tree which gives insight on how the data is derived and should facilitate error resolution in complicated components Test Plan: Added a test case where we were failing to track derivations. Also updated the test cases with the new error containing the data flow tree
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary:
Revamped the derivationCache graph.
This fixes a bunch of bugs where sometimes we fail to track from which props/state we derived values from.
Also, it is more intuitive and allows us to easily implement a Data Flow Tree.
We can print this tree which gives insight on how the data is derived and should facilitate error resolution in complicated components
Test Plan:
Added a test case where we were failing to track derivations. Also updated the test cases with the new error containing the data flow tree
Stack created with Sapling. Best reviewed with ReviewStack.
no-deriving-state-in-effects#34995