Jimmy Jia

If you use the Babel transform per https://github.com/4Catalyzer/astroturf#use-without-webpack, you'll end up with a bunch of little split-out CSS files. You'd need to either do something BEM-y in naming the classes,...

i mean, it's definitely neat. if you wanted to do something more robust, you could possibly use something like the existing JSX transform to convert all the props into a...

Well, it's zero-runtime if you use the CSS tag. I feel like a nice API is possible, though. Something like: ```js function MyComponent(props) { const className = useStyled` color: black;...

I wonder if we could be really clever here and just support: ``` ```

@ivancuric Thanks! I edited @jquense's comment.

We discussed this in https://github.com/4Catalyzer/astroturf/pull/348#issuecomment-520862383 as well. The issue with using a different template tag is that it wouldn't integrate with existing tooling.

How would you cross-reference those classes above with that object syntax though? I guess you'd do something like: ```js const className1 = css`...`; const className2 = css`...`; ``` instead of...

How much do you think it would break if we were to whitelist certain bindings like `styles` or `fooStyles` that would keep the old behavior?

So would it be terrible to check the variable name ending with `/[sS]tyles$/` and build to a single class otherwise?

right, i don't really see the point...