-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
Non-updated state treated differently in different places #14280
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
Comments
Similarly, I think it'd be useful if we determined when any state updates happen to see if we really need to make a value a let a = $state(1);
a++;
//becomes
let a = 2; //assuming `a` doesn't update anywhere else |
Out of curiosity, is there a reason you chose to use |
Describe the bug
Minor, but given a component like this...
...neither
a
norb
is turned into state, because they are never updated. But the contents of the<p>
are put in an effect anyway:Whatever logic is used for determining whether it's
a = 1
ora = $.state(1)
should also be used for determining whether to create an effect.Reproduction
link
Logs
No response
System Info
Severity
annoyance
The text was updated successfully, but these errors were encountered: