-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
$derived rune stops working but not if using $inspect() #12044
Comments
I could be wrong, but it could be due to potential runtime reactivity issues. |
I'm a hobby coder. Can you point me in the right direction if there's an article or post about this... And how to fix? |
@aadtyaraj01 I am not a member of the core team. I would wait for an official response from one of the maintainers before giving advice. |
I guess this REPL is a simpler version of what is provided.
Doing one of the following changes makes 1-5 work (doesn't matter which one):
|
I've had something similar, but haven't been able to create a cut-down reproduction yet. In my case a page refresh results in reactivity sometimes works and sometimes doesn't, same code, same data. Adding an inspect on a dependency of the derived that isn't updating makes it work consistently, so it looks like it's losing track of the dependency or change notification somewhere along the line. It's also with things using Unless this is just a bug, remember when you do things like |
Here's what happens for me - there is a chain of |
Does this mean it's fixed now? Hobby coder 😅 Also, I used a function to return the value instead of the derived rune. And it works fine.
|
Yes it should be fixed, update to the latest version to see it in effect |
It's not published on npm yet |
Describe the bug
I'm creating a toggle button that toggles different menu into view.
The button stops toggling.
But when I use insect or log the derived rune, it works.
Reproduction
Go to the /posts route please. In the bottom left corner is the button which gets the error.
StackBlitz .
And here's the recording too:
Jam Dev
Logs
System Info
Severity
blocking an upgrade
The text was updated successfully, but these errors were encountered: