The regular rule test should be as bland as possible#278
Merged
nzakas merged 2 commits intoCSSLint:masterfrom May 21, 2012
Merged
The regular rule test should be as bland as possible#278nzakas merged 2 commits intoCSSLint:masterfrom
nzakas merged 2 commits intoCSSLint:masterfrom
Conversation
…avoids conflicts with rules about naming conventions.
nzakas
added a commit
that referenced
this pull request
May 21, 2012
The regular rule test should be as bland as possible
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I got a custom rule which checks if you're adhering to some naming conventions. A ruleset like:
.foo { width: 100px; }(which is currently used by tests/all-rules.js) does trigger a warning.I replaced it with that kind of rule everyone is using:
body { margin: 0; }.That was the most neutral thing I could think of.