-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
feat(v2): new signals implementation #6443
Conversation
bee49ed
to
e9a5fe4
Compare
@JerryWu1234 right that's the idea, we were having trouble getting signals to work so we decided to improve the implementation |
d5db08c
to
defd5cf
Compare
|
6d2ec35
to
9b5e492
Compare
fix store deserialization without effects Co-authored-by: Jack Shelton <thejackshelton@users.noreply.github.com> Co-authored-by: Wout Mertens <Wout.Mertens@gmail.com>
Co-authored-by: Jack Shelton <thejackshelton@users.noreply.github.com>
commit: |
built with Refined Cloudflare Pages Action⚡ Cloudflare Pages Deployment
|
Overview
This is an exploration (may not land) the Signal implementation for something more clear / more maintainable.
Todo:
.only
Note about cross-container support: because:
, the only way to communicate between containers is with custom events like
"q-signal:my- global-name"
that dispatch signal values. This would be another effect handled by a separate GlobalSignal.