Skip to content
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: rework bindable types strategy #2361

Merged
merged 5 commits into from May 2, 2024
Merged

Conversation

dummdidumm
Copy link
Member

Instead of using types that declare whether or not a type is bindable directly as part of the property, we're introducing a new for-types-only field to SvelteComponent: $$bindings, which is typed as the keys of the properties that are bindable (string by default, i.e. everything's bindable; for backwards compat). language-tools can then produce code that assigns to this property which results in an error we can display if the binding is invalid. This means we can revert a lot of the changes we made to make the previous version of bindable types work

Instead of using types that declare whether or not a type is bindable directly as part of the property, we're introducing a new for-types-only field to `SvelteComponent`: `$$bindings`, which is typed as the keys of the properties that are bindable (string by default, i.e. everything's bindable; for backwards compat). language-tools can then produce code that assigns to this property which results in an error we can display if the binding is invalid.
This means we can revert a lot of the changes we made to make the previous version of bindable types work
@dummdidumm dummdidumm marked this pull request as ready for review May 2, 2024 16:06
@dummdidumm dummdidumm merged commit 9d7907e into master May 2, 2024
3 checks passed
@dummdidumm dummdidumm deleted the bindable-types-rework branch May 2, 2024 16:08
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.

None yet

1 participant