Monte

Perhaps I'm missing something here, but it seems like the only modification to `css` needed is that it join any string arguments passed to it onto the resulting class name...

Ah, yes I understand now. Thanks for taking the time to explain! In that case, @jlfwong's idea: > One option is to make css remember not only which classnames it's...

One issue will be with server side rendering. Once we are on the client, there will be no way of determining which JS objects generated the `renderedClassNames` at the call...

Agreed! Another issue: what to do when a string passed to `css` is a CSS class name that was **not** generated by aphrodite? For example, somebody using an external CSS...

I completely agree. Just figured I'd throw something out there to try and get the ball rolling towards a more realistic solution :)

This pattern of merging default styles with styles passed in as props is common in my projects. In most cases, I have access to the JS style objects, and so...

I'm wondering if anybody has alternate patterns that might altogether sidestep this issue? What does the Khan Academy team do (or not do) about this?

@Fil - Thanks for the quick turn around :) ### The number of errors 58 of those 66 errors you mention are from the `strictNullChecks`, whereas the remaining `8` are...