Fredrik Nicol

It's a bit complicated to implement, yes. But I've made some progress and I'm planning to resume that work after I my vacation. Hopefully! 😸 That case you're suggesting doesn't...

I don't consider this a breaking change in a typing perspective. Then basically all changes should be considered breaking. The type safety issue should be solved with literal template types...

Does this command `$ npx flow check __tests__/__fixtures__/typecheck.js` work?

If Flow isn't supported on ppc64le then I can't help you, sorry. You should reach out to https://github.com/facebook/flow for guidance.

Hopefully this could be solved with template literal types in the future. But it requires some additional work before we can use template literal types.

As soon as I have time to fix it. Soon I hope. That's not true. The [`display` property](https://developer.mozilla.org/en-US/docs/Web/CSS/display#syntax) accepts a two-value syntax even though it's rarely used. That's why `string...

It's pretty intense to generate a union for every possible combination for every property of this kind. That's why literal template types will come in handy.

What's the status of this?

It would be really cool if it also could optimize media queries, if you were nesting them using SASS. E.g. ``` sass @mixin gutter { margin-right: 1rem; @media (min-width: 320px)...

There's similar [solution in Glitz](https://github.com/frenic/glitz/blob/734e0a5344b9096135958f3ae46470cd361da86e/packages/react/src/styled/create.ts#L93-L106). But it renders inline `` tags which hydrates this into `` and gets removed later on. It works quite well too.