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.

Sign up for GitHub

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

Jump to bottom

useState is not reactive #169

Closed
Rigo-m opened this issue Nov 24, 2021 · 0 comments · Fixed by nuxt/framework#2134
Closed

useState is not reactive #169

Rigo-m opened this issue Nov 24, 2021 · 0 comments · Fixed by nuxt/framework#2134
Labels
bridge pending triage

Comments

@Rigo-m
Copy link
Contributor

Rigo-m commented Nov 24, 2021 •
edited

Environment

Any nuxt2 + bridge environment

Reproduction

codesandbox

Describe the bug

useState creates a new nuxtApp.payload.useState entry automatically via toRef, but it's not reactive (computed and watch methods doesn't trigger). Fixable via the set composable.

Additional context

Related to vuejs/composition-api#855

Logs

No response
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bridge pending triage
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix(bridge): fixed reactivity on csr of useState reactive payload Rigo-m/framework
1 participant
@Rigo-m