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
Ideally in projects like Studio we'd only use Assembly classes, or a small amount of custom CSS. Sadly sometimes things in className={} are misnamed or don't actually exist.
I think we should make an ESLint plugin that checks all className={} and classnames statements to ensure all classes are valid in MBX Assembly.
An escape hatch could be an ESLint option that accepts additional class names.
The text was updated successfully, but these errors were encountered:
I think it would be cool if this were generalized beyond just Assembly, like a eslint-plugin-atomiccss or something where you just pass a list of CSS files and it scans class names.
Also need to double check if it supports JSX and classnames helper.
Description
Ideally in projects like Studio we'd only use Assembly classes, or a small amount of custom CSS. Sadly sometimes things in
className={}
are misnamed or don't actually exist.I think we should make an ESLint plugin that checks all
className={}
andclassnames
statements to ensure all classes are valid in MBX Assembly.An escape hatch could be an ESLint option that accepts additional class names.
The text was updated successfully, but these errors were encountered: