chore: add basic config for stylelint
#996
Draft
+418
−78
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
This PR introduces
stylelint
to help ensure CSS is written according to our standards and without unintentional errors.We currently have a bunch of bad CSS (in template literals). To not depend on the built-in abilities of some IDEs,
stylelint
ensures that the quality of our styles is on par with the code that we expect to passeslint
.Which issue(s) this PR fixes:
Issues with CSS written as CSS (whether it be inside template literal or in .css files).
How to test
nvm use
yarn
yarn stylelint
Note: this does not address the weak "type safety" of Object style usage of
emotion/css
Note: I expect us to tweak and test
stylelint
before we (potentially) decide to merge it.