-
Notifications
You must be signed in to change notification settings - Fork 3
fix: check effect.pre in assign-in-effect #41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
It seems like the intention here was to check `$effect` _and_ `$effect.pre`, but the condition (`in_effect`) was filtering those out. The `is_rune` helper already does the same checks, so we can just remove the ones here and delegate to that.
🦋 Changeset detectedLatest commit: f3ee4ed 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 |
@43081j is attempting to deploy a commit to the Svelte Team on Vercel. A member of the Team first needs to authorize it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Good catch!
The latest updates on your projects. Learn more about Vercel for GitHub.
|
@43081j can you fix the lint issues? |
ironically the error was that the changeset wasn't formatted 😅 should be fixed now |
Duh...I need to ignore changesets |
It seems like the intention here was to check
$effect
and$effect.pre
, but the condition (in_effect
) was filtering those out.The
is_rune
helper already does the same checks, so we can just removethe ones here and delegate to that.
If we don't want to report on
effect.pre
, i can rework this to just remove the'$effect.pre'
from the list of runes.