docs: Update $props documentation to clarify when prop values are deeply re… #13994
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 PR updates the $props documentation to clarify when prop values are deeply reactive
In particular, this wording confused me:
As I took it to be an exception, implying that non-fallback values are turned into reactive state proxies. Some experimentation revealed that this is not the case.
Side note: this is my first contribution, I'm new to svelte and reading a lot of docs and happy to help improve them where I'm able. If it would be preferable to discuss docs improvements before opening a PR, please let me know where best to open the discussion.
Before submitting the PR, please make sure you do the following
feat:
,fix:
,chore:
, ordocs:
.Tests and linting
pnpm test
and lint the project withpnpm lint