-
-
Notifications
You must be signed in to change notification settings - Fork 219
fix(svelte2tsx): support for runes={false} in svelte:options #2847
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
fix(svelte2tsx): support for runes={false} in svelte:options #2847
Conversation
Signed-off-by: axel7083 <42176370+axel7083@users.noreply.github.com>
🦋 Changeset detectedLatest commit: 8e59b25 The changes in this PR will be included in the next version bump. This PR includes changesets to release 4 packages
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 |
Signed-off-by: axel7083 <42176370+axel7083@users.noreply.github.com>
Pretty weird that |
Signed-off-by: axel7083 <42176370+axel7083@users.noreply.github.com>
@dummdidumm I updated the failing test 👍 |
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.
thank you!
Signed-off-by: axel7083 <42176370+axel7083@users.noreply.github.com>
@dummdidumm I added the |
@dummdidumm yeahh all tests are passing :p |
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.
thank you!
Description
The
<svelte:options runes/>
were not checking for the value, so it was always true. When using<svelte:options runes={false}/>
the props exported wereRecord<string, never>
which is incorrect.Related issues
Fixes #2843
Testing