Skip to content

fix: reactive ref should be an instance of Reactive to work with use_reactive#544

Merged
maartenbreddels merged 1 commit intomasterfrom
03-07-fix_reactive_ref_should_be_an_instance_of_Reactive_to_work_with_use_reactive
Mar 8, 2024
Merged

fix: reactive ref should be an instance of Reactive to work with use_reactive#544
maartenbreddels merged 1 commit intomasterfrom
03-07-fix_reactive_ref_should_be_an_instance_of_Reactive_to_work_with_use_reactive

Conversation

@maartenbreddels
Copy link
Copy Markdown
Contributor

This make the todo app fail, since it would wrap the ref in a reactive
var.

Copy link
Copy Markdown
Contributor Author

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @maartenbreddels and the rest of your teammates on Graphite Graphite

…reactive

This make the todo app fail, since it would wrap the ref in a reactive
var.
@maartenbreddels maartenbreddels force-pushed the 03-07-fix_reactive_ref_should_be_an_instance_of_Reactive_to_work_with_use_reactive branch from 951966e to 5831119 Compare March 7, 2024 12:50
@maartenbreddels maartenbreddels merged commit 7592d49 into master Mar 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant