docs: Add prominent link to svelte/reactivity from state #16220
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This risks overlapping with #13571 but the
svelte/reactivitydocs page still risks being a content island, which is a shame since tools likeSvelteMap,SvelteSetare an incredibly natural go-to.This change to the $state docs would follow my natural mental model, if i'm discovering Svelte today for the first time or on a refresher course.
"Great, runes exist. State is a rune for setting the reactive source. What if I want to use $state for one thing? Ok, now what if I want to use $state for many things at once?"
I suggest an outright section "State for Collections" inside the $state doc page.