-
-
Notifications
You must be signed in to change notification settings - Fork 95
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
Removed difference in behaviour of @preact/signals and @preact/signal… #387
Removed difference in behaviour of @preact/signals and @preact/signal… #387
Conversation
🦋 Changeset detectedLatest commit: 7d5ad6e The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
✅ Deploy Preview for preact-signals-demo ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
@andrewiggins i think it has no performance overhead in case of rendering string into Text nodes directly, but adds oprtunity to render jsx inside signal. There are oprtunity when chaning signal type |
I will add |
@JoviDeCroock please check this PR 🙏🙏🙏 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for review
Fixed comments @JoviDeCroock |
This also needs a changeset and probably a rebase/merge so the netlify checks start succeeding |
…e-difference-in-behaviour-between-adapters
@JoviDeCroock please check) |
we don't need to talk about these to the outside world
Resolves ##383
When we return a VNode in a signal/computed we would incorrectly try to treat this as a text-node, which would result in us incorrectly triggering changes