Andy Wermke

@Janpot Thanks for your feedback! > I would prefer to see an API where there's a hook per class. Good news. There is! 😉 Check out [`useStyle()`](https://github.com/andywer/react-usestyles/blob/master/packages/style-hook/README.md#usestyle).

@tomByrer Interesting point! And thx for the links 🙂 I created a follow-up issue for the composablity: #4. I don't think it's that hard to find a solution for it,...

Well, one of the main goals of this hook is to come up with an API that is so generic, yet convenient to use, that it might be considered a...

Currently aiming for a standard API only (the hook, the loosely coupled styling lib integration + how the style objects look like). How the users create the style object is...

Hey @brandonkal. Thanks for the comprehensive feedback! At first a question, though. What is that syntax that you mentioned supposed to do / to work: ``` ${[props.primary]} { background-color: blue;...

I recently came up with new API idea that solves some issues we had before. Tell me what you think. ```jsx import Styled from "..." export default Styled(function Button(props, Style)...

PS: The idea of a higher order function passing additional gizmos to a component as a second parameter exists already, actually. Take [`React.forwardRef()`](https://reactjs.org/docs/react-api.html#reactforwardref), for instance. It's just uncommon to pass...

Thanks for sharing, Brandon! But honestly, I wouldn’t care about extracting the static CSS bits at build time too much for now. SSR can work anyway and performance-wise the big...

> It appears to couple the component to whatever styling library Styled function comes from. No, this is the whole point of this project – providing a library with one...

Posted the concept for a different API change (see #5) that allows a couple of improvements over the current API and that I feel more comfortable with than the concept...