Callan Delbridge
Callan Delbridge
I'll note that you can get around this by creating a component for `createElement`, like below: ```jsx const CreateElement = ({ element, children, ...restProps }) => { return React.createElement( element,...
Thanks for the reply! My naive solution, and I don't have too much experience writing Babel transforms so I couldn't comment on the complexity of this, would be to convert...
One workaround that the library I linked to uses is to name each of the stylesheet imports, and reference them as `foo.red` and `bar.wrapper`, like: ```js import foo from './foo1.css';...
I like the idea of using the `styleName` prop for all of this as it still allows people to access the natural behaviour of `className` on `.web` files if they...
Thanks, sure thing! Here's a fairly comprehensive list: -- **Unnamed import with single class hardcoded** ```jsx import './Button.css'; Foo ``` **Unnamed import with single class as variable** ```jsx import './Button.css';...
So it would be a runtime vs compilation time issue? So, the `classnames` fn will return to us a string when it's called in the browser/phone instead of on build...
Just want to note quickly that I haven't forgotten about this and plan to do some work but haven't been able to get around to it yet!