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
{{ message }}
This repository has been archived by the owner on Jun 17, 2019. It is now read-only.
eslint can be very effective to enforce some conventions. We're already using it to verify if a component's name is the same of its filename.
New rules to help us enforce some conventions::
a Component can import only one sass file and only if it has the same name (but in camelCase)
ex: MyBeautifulComponentcan have import './myBeautifulComponent.scss'
the imported sass must be in the same folder (./*.scss)
if a component has a main class, this should be the component's name in kebab-case
ex: MyBeautifulComponentcan have <div className='my-beautiful-component' ...
The text was updated successfully, but these errors were encountered:
original issue: https://github.omnilab.our.buildo.io/buildo/labonline/issues/1305
requirements
eslint
can be very effective to enforce some conventions. We're already using it to verify if a component's name is the same of its filename.New rules to help us enforce some conventions::
sass
file and only if it has the same name (but incamelCase
)MyBeautifulComponent
can haveimport './myBeautifulComponent.scss'
sass
must be in the same folder (./*.scss
)kebab-case
MyBeautifulComponent
can have<div className='my-beautiful-component' ...
The text was updated successfully, but these errors were encountered: