Skip to content

fix: correctly handle SvelteDate methods with arguments #12738

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

Merged
merged 5 commits into from
Aug 5, 2024
Merged

Conversation

trueadm
Copy link
Contributor

@trueadm trueadm commented Aug 5, 2024

Fixes #12717. We shouldn't cached deriveds for methods that take params, oops.

Copy link

changeset-bot bot commented Aug 5, 2024

🦋 Changeset detected

Latest commit: 0f1a1d9

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
svelte Patch

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

@Rich-Harris
Copy link
Member

Surely if we're not caching we shouldn't be creating the derived?

@trueadm
Copy link
Contributor Author

trueadm commented Aug 5, 2024

Surely if we're not caching we shouldn't be creating the derived?

Addressed

Co-authored-by: Rich Harris <rich.harris@vercel.com>
@trueadm trueadm merged commit e78cfd3 into main Aug 5, 2024
9 checks passed
@trueadm trueadm deleted the fix-date branch August 5, 2024 16:03
This was referenced Aug 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

SvelteDate behaving weirdly (reactivity issue)
2 participants