-
Notifications
You must be signed in to change notification settings - Fork 1.4k
fix: reactivity after spreading props #7809
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
Conversation
🦋 Changeset detectedLatest commit: 1a0ee9b The changes in this PR will be included in the next version bump. 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 |
6846f0c
to
6cc7bd0
Compare
built with Refined Cloudflare Pages Action⚡ Cloudflare Pages Deployment
|
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.
Looking great, just wondering about making var mutable?
packages/qwik/src/optimizer/core/src/snapshots/qwik_core__test__example_jsx.snap
Outdated
Show resolved
Hide resolved
6cc7bd0
to
feae538
Compare
commit: |
feae538
to
65f073d
Compare
…in JSX components
65f073d
to
1a0ee9b
Compare
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.
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.
@Varixo 👏 you are amazing 🤩
Spread props caused calling get trap for every props property. It means propsproxy will unwrap signals and pass flat value instead. Now we are using new _getVarProps, _getConstProps functions to direct get props object instead of using proxy