Skip to content

docs: clarify why we need to use the derived rune #13919

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

Merged

Conversation

stephane-vanraes
Copy link
Contributor

In the v4 docs it was clearly explained why we need to use $: to re-evaluate assignments, this is missing for the $derived rune and could be a pitfall for people new to the framework.

Note: should be fixed in the tutorial as well.

Copy link

changeset-bot bot commented Oct 25, 2024

⚠️ No Changeset found

Latest commit: be931e3

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

Copy link

pkg-pr-new bot commented Oct 25, 2024

pnpm add https://pkg.pr.new/svelte@13919

commit: be931e3

@dummdidumm
Copy link
Member

I think it makes sense to mention this, but we shouldn't begin with it.

@stephane-vanraes
Copy link
Contributor Author

@dummdidumm the current change is basically copypasta from the old docs. Maybe a short explanation can be formatted as note (the ones with the lightbulb) like done in $inspect when mentioning it will be noop'ed in production

@dummdidumm dummdidumm merged commit feb2d85 into sveltejs:main Oct 25, 2024
9 checks passed
@dummdidumm
Copy link
Member

thank you!

@stephane-vanraes stephane-vanraes deleted the clarify_the_need_of_derived branch October 25, 2024 10:03
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.

2 participants