Skip to content
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

fix: reactivity of useState is not populated properly #643

Open
kleinpetr opened this issue Apr 1, 2024 · 0 comments · May be fixed by #663
Open

fix: reactivity of useState is not populated properly #643

kleinpetr opened this issue Apr 1, 2024 · 0 comments · May be fixed by #663
Labels
bug Something isn't working

Comments

@kleinpetr
Copy link

🐛 The bug

When I change the value in the useState, inside a compsable, the new value is not populated proeprly.

Reproduction process

  1. open devtools -> payload and see test-my-test
  2. click Update button
  3. reload value in the devtools (it's still empty)

🛠️ To reproduce

https://stackblitz.com/~/github.com/kleinpetr/nuxt-playground/tree/devtools-usestate-reactivity

🌈 Expected behavior

I would expect the property is being updated.

ℹ️ Additional context

When you reload the page with closed devtools, then hit the Update button and then open them, the value is there and when you click for example to Add string and reload the value, it works correctly but once you hit the Update button again and then reload value in devtools it's stucked.

@kleinpetr kleinpetr added the bug Something isn't working label Apr 1, 2024
@hichem-dahi hichem-dahi linked a pull request May 13, 2024 that will close this issue
hichem-dahi pushed a commit to hichem-dahi/devtools that referenced this issue May 15, 2024
hichem-dahi pushed a commit to hichem-dahi/devtools that referenced this issue May 16, 2024
hichem-dahi pushed a commit to hichem-dahi/devtools that referenced this issue May 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant