Provide a stylelint config that we can tweak #2138
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pablobm
force-pushed
the
stylelint-config
branch
2 times, most recently
from
85b006b to
cab45b4
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Over at #2116, Hound is being very noisy about automatically-generated CSS that we can't control.
It looked like the issue could be scss-lint, which is specifically configured in
.hound.yml. However I looked up the warning messages and actually they come from stylelint. I have no idea of what configuration of stylelint is being used, but I figured that we can import thoughtbot's one as a baseline. So here it is. Now we have a way to explicitly tell Hound to be silent about specific files.