docs: remove section on callbacks and accessor bindings #10750
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
$effect
docs are completely overwhelming. If we want to discourage use of something, we should spend a lot less time talking about it — instead, we currently spend way more time talking about$effect
than any other rune.In particular, I think this section is unnecessary. The example doesn't really resemble anything you'd find in real code, and it makes everything seem a lot more complicated than it needs to be. We should also avoid making up terms like 'writable
$derived
' without explaining them.When we update the tutorial to cover Svelte 5, we can afford to spend time in more of these nooks and crannies. Until then, we should remove this.