Explicit, framework agnostic, CSS-in-JS support #12
Labels
enhancement
New feature or request
help wanted
Extra attention is needed
will need tests
Will require associated unit/integration tests for changed/added behaviour.
Milestone
Currently our CSS-in-JS support relies on user's bootstrapping their own implementation using the
resolveBp
function export. For official support, we'll need to have a proper review of it in practice with popular CSS-in-JS frameworks: at the very least Emotion and Styled Components.Ideally this comes down to something like just three functions:
cq(query, bpName)
a.k.a. container query, (also known as bpc) which conditionally returns a CSS block based on the provided querymq(query)
a.k.a. media query, which returns a legit CSS media query blockFor SCSS support, we might need to add a third mixin for the app container. Really there are three use-cases here overall:
But for SCSS we'll need to add a third mixin targeting the className injected by the AppContainer to support the above.
The text was updated successfully, but these errors were encountered: