-
-
Notifications
You must be signed in to change notification settings - Fork 37
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
Allow nested selectors #13
Conversation
Actually if I change: getCssObjectOrCssObject:
| ((
theme: Theme,
params: Params,
classes: Record<Key, string>, // <-- here
) => Record<Key, CSSObject>)
| Record<Key, CSSObject>, to: getCssObjectOrCssObject:
| ((
theme: Theme,
params: Params,
classes: any,
) => Record<Key, CSSObject>)
| Record<Key, CSSObject>, But I am not totally sure why that happens. Also any seems like not the right choice here but it does get it working. |
b2473cf
to
132e4d9
Compare
Damn, |
I am very disappointed 😞 |
Calling I am going to run this in the meantime, until a better API emerges. |
132e4d9
to
4f9f034
Compare
@garronej also, I pushed up the change from You might still consider a merge and then a minor version bump later in the case of a better API. |
Hold on a minute, I want to know what you think about this |
Seems fine to me if it gets the job done! |
I test it and release it in the next hour. |
I will merge even if I override it. This way you'll appear in the contributor list. |
@garronej this seems to work, by calling emotion
css
function twice - but it breaks the types.