Kristóf Poduszló

Awesome, I really love this idea! It would allow conditional rules to be defined in any order without issues. (A mobile-first approach is still recommended and should possibly generate a...

Thank you for the idea! I was thinking anout a plugin system during the initial development phases, but decided against them to reduce the scope of the library. Auto-prefixing is...

Whoa, this is truly remarkable, thank you! While I’m not sure about the static analysis benefits this provides, a `composeCSS` function would be nice to have in v1 or v2....

Thank you for sharing your thoughts in detail, @etc-tiago! While object spreading is possible, someone may decide to pass stringified class names generated by otion to a component, e.g.: ```tsx...

@eddyw Thank you for your great work and the PR for making that concept a reality. I decided to rewrite otion from the ground up with high test coverage and...

Unlike in most existing solutions, the `css` prop [should be passed between components](https://twitter.com/tibfib/status/1262138540403507200) for atomic composability.

Thank you for these detailed thoughts. The `css()` API would be great if composition can be solved. For example, when component `A` passes `padding: 16` to component B which already...

Shorthands are hard to handle. I’m not quite sure about how they should be managed. Composition feels a bit unnatural for atomic CSS. Your idea sounds awesome, but it seems...

It seems this could be done [with a Babel macro](https://twitter.com/kuldeepkeshwar/status/1291688956073893893). As for ideas about resolving composition, please [see issue #47](https://github.com/kripod/otion/issues/47#issuecomment-667654260).

Awesome, I love how fast you're delivering improvements 🙌