You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
it'd be super practical, if we'd split the code formatting config from the BEM naming config.
We don't use this package right now in e.g. React projects, where we use component based style loading and therefore don't need BEM.
However it would be great, if we included a default code formatting configuration, that provides default configurations for our CSS files.
I'd suggest to split this package into two separate ones: one for BEM and the other for basic CSS code formatting.
The text was updated successfully, but these errors were encountered:
Hey,
it'd be super practical, if we'd split the code formatting config from the BEM naming config.
We don't use this package right now in e.g. React projects, where we use component based style loading and therefore don't need BEM.
However it would be great, if we included a default code formatting configuration, that provides default configurations for our CSS files.
I'd suggest to split this package into two separate ones: one for BEM and the other for basic CSS code formatting.
The text was updated successfully, but these errors were encountered: