-
-
Notifications
You must be signed in to change notification settings - Fork 29
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
Reconsider the API for interpolation #37
Comments
Briefly, the nice thing about interpolation today is it's free-form and doesn't force a user into building components a specific way. For instance, I can do a selector like Based on this, I don't think it's possible to do things like that - unless we treat Why couldn't every other selector just be this? I think TypeScript should provide the autocompletion anyway once it sees that it's not an array or primitive. If it doesn't, that might an enhancement request, but I'm pretty sure it does 😄 [selector: string]: undefined | number | string | (number | string)[] | NestedCSSProperties Is there any other goals, other than simpler auto-completion? |
I can understand if this should be closed as it can be done in userland quite easily. Neverthless I wanted to leverage your opinion on something like the following for interpolation :
Example:
The current implementation is not amenable for typing:
Again, thanks for being so awesome 🌹
The text was updated successfully, but these errors were encountered: