docs: move some $state information around
#15969
Merged
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
|
Contributor
|
Co-authored-by: Paolo Ricciuti <[email protected]>
elliott-with-the-longest-name-on-github
approved these changes
May 23, 2025
elliott-with-the-longest-name-on-github
merged commit 08346b5
into
main
13 checks passed
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.
Was just reading https://svelte.dev/docs/svelte/$state and I really don't like the 'Class instances are not proxied' breakout quote. It doesn't make sense to disrupt the flow with noise about classes at this point, and it's redundant — the very next sentence is "State is proxified recursively until Svelte finds something other than an array or simple object".
Verdict: get rid of it