feat: turn reactive_declaration_non_reactive_property into a runtime warning
#14192
+217
−82
Conversation
This file contains 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
🦋 Changeset detectedLatest commit: 2207b7d The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
preview: https://svelte-dev-git-preview-svelte-14192-svelte.vercel.app/ this is an automated message |
|
dummdidumm
reviewed
Nov 6, 2024
Co-authored-by: Simon H <5968653+dummdidumm@users.noreply.github.com>
Co-authored-by: Simon H <5968653+dummdidumm@users.noreply.github.com>
dummdidumm
reviewed
Nov 7, 2024
|
I agree this approach makes sense |
This was referenced Nov 9, 2024
This was
linked to
issues
Nov 9, 2024
Co-authored-by: Simon H <5968653+dummdidumm@users.noreply.github.com>
dummdidumm
approved these changes
Nov 25, 2024
Merged
6 tasks
dummdidumm
added a commit
that referenced
this pull request
Dec 10, 2024
…warning fixes #14532 This removes the `reactive_declaration_non_reactive_property` warning altogether. The first version caused many false positives at compile time. The refined runtime version (introduced in #14192) was hoped to fix this, but it turns out we now get loads of false positives at runtime. The ones I've seen essentially revolve around a signal being created while reading or writing (to) something in a reactive statement, but in a matter which is harmless. For example writing to `$$props` or `$$restProps` (like `$: { if ($$restProps.foo) $$restProps.bar = 'x' }`) creates a new signal under the hood, as the props now temporarily can get out of sync, and we need a backing signal for that. For this we call the `prop` function, which in turn creates several deriveds and may also read from user-land signals that were not read previously - in other words, it's not possible to fix the problem by marking all internal signals (which would be a very very tedious undertaking). The potential benefits of this warning are vastly outnumbered by the false positives it causes, so we should just remove it.
6 tasks
dummdidumm
added a commit
that referenced
this pull request
Dec 11, 2024
…warning (#14663) fixes #14532 This removes the `reactive_declaration_non_reactive_property` warning altogether. The first version caused many false positives at compile time. The refined runtime version (introduced in #14192) was hoped to fix this, but it turns out we now get loads of false positives at runtime.
wackbyte
added a commit
to wackbyte/anki
that referenced
this pull request
Jan 12, 2025
Warnings from enums were fixed in sveltejs/svelte#14192
wackbyte
added a commit
to wackbyte/anki
that referenced
this pull request
Jan 12, 2025
Warnings from enums were fixed in sveltejs/svelte#14192
dae
pushed a commit
to ankitects/anki
that referenced
this pull request
Jan 12, 2025
Warnings from enums were fixed in sveltejs/svelte#14192
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.
Alternative to #14111. Instead of a compiler warning, we can have a runtime warning for cases where 'invisible' reactive state is read inside a
$:statement. The message could probably be improved and it might be nice to have a detailed example for the docs, but putting this up just as a suggestion for nowBefore submitting the PR, please make sure you do the following
feat:,fix:,chore:, ordocs:.Tests and linting
pnpm testand lint the project withpnpm lint