-
-
Notifications
You must be signed in to change notification settings - Fork 4.7k
docs: $props
destructuring is reactive
#16901
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
⚠️ No Changeset found
Latest commit: 8b42d42
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
pnpm add https://pkg.pr.new/svelte@16901
Does this really need spelling out? This hasn't been a point of confusion, to my knowledge. If we add callouts for everything, people will develop a blindness to them
I still think it's magical and would be nice if it was specified in the docs.
Especially since $props
is the only runes API that kind of requires destructuring (data
, params
, etc.)
Maybe adding the following section from $derived
in both $state
and $props
could be the way to go:
If you use destructuring with a
$derived
declaration, the resulting variables will all be reactive — this...
I was reading through the docs, and reading that section was a aha moment for me that $props
destructuring pretty much works the same way.
Unlike
$derived
,the
$props
documentation does not specify that the destructured variables are reactive. This is all it says:Before submitting the PR, please make sure you do the following
feat:
,fix:
,chore:
, ordocs:
.packages/svelte/src
, add a changeset (npx changeset
).Tests and linting
pnpm test
and lint the project withpnpm lint