|
1 | | -[](https://www.npmjs.com/package/csslint) |
2 | | -[](https://travis-ci.org/CSSLint/csslint) |
3 | | -[](https://david-dm.org/CSSLint/csslint) |
4 | | -[](https://david-dm.org/CSSLint/csslint#info=devDependencies) |
5 | | - |
6 | | -# CSSLint |
7 | | - |
8 | | -CSSLint is an open source CSS code quality tool originally written by |
9 | | -[Nicholas C. Zakas](http://www.nczonline.net/) and |
10 | | -[Nicole Sullivan](http://www.stubbornella.org/). It was released in June 2011 at |
11 | | -the Velocity conference. |
12 | | - |
13 | | -A [lint](http://en.wikipedia.org/wiki/Lint_programming_tool) tool performs |
14 | | -[static analysis](http://en.wikipedia.org/wiki/Static_code_analysis) of source |
15 | | -code and flags patterns that might be errors or otherwise cause problems for the |
16 | | -developer. |
17 | | - |
18 | | -CSSLint is a tool to help point out problems with your CSS code. It does basic |
19 | | -syntax checking as well as applying a set of rules to the code that look for |
20 | | -problematic patterns or signs of inefficiency. The rules are all pluggable, so |
21 | | -you can easily write your own or omit ones you don't want. |
22 | | - |
23 | | -## Integration |
24 | | - |
25 | | -### Command Line Interface |
26 | | - |
27 | | -All about the command line interface for CSSLint. If you'd rather use a CLI |
28 | | -program to verify your CSS instead of using the web site, then this guide is |
29 | | -your best friend. |
30 | | -https://github.com/CSSLint/csslint/wiki/Command-line-interface |
31 | | - |
32 | | -### Build System |
33 | | - |
34 | | -Once you're familiar with the CSSLint command line interface, the next step is |
35 | | -to integrate it into your build system. This guide walks through using CSSLint |
36 | | -as part of your build. |
37 | | -https://github.com/CSSLint/csslint/wiki/Build-System-Integration |
38 | | - |
39 | | -### IDE |
40 | | - |
41 | | -You can integrate CSSLint into your favorite IDE to make checking your CSS code |
42 | | -quality easy. In fact, some IDEs already have CSSLint built in. |
43 | | -https://github.com/CSSLint/csslint/wiki/IDE-integration |
44 | | - |
45 | | -## Rules |
46 | | - |
47 | | -Not sure why a rule is important? This guide talks about each of the CSSLint |
48 | | -rules and explains how the rule is designed to improve your CSS. |
49 | | -https://github.com/CSSLint/csslint/wiki/Rules |
50 | | - |
51 | | -## Developer Guide |
52 | | - |
53 | | -If you want to contribute to the project, or even just tinker on your own, |
54 | | -this guide explains how to get the source and work with it. |
55 | | -https://github.com/CSSLint/csslint/wiki/Developer-Guide |
56 | | - |
57 | | -## Contributors |
58 | | - |
59 | | -1. Samori Gorse, https://twitter.com/shinuza (Rules, Non-zero Exit Code for CLI) |
60 | | -1. Eitan Konigsburg, https://twitter.com/eitanmk (Rhino CLI) |
61 | | -1. Ben Barber (Compatible Vendor Prefix Rule) |
62 | | -1. Eric Wendelin, http://eriwen.com (Output formatters) |
63 | | -1. Kasper Garnaes, http://reload.dk (Checkstyle XML format) |
64 | | -1. Gord Tanner, http://www.tinyhippos.com (CLI quiet option) |
65 | | -1. Hans-Peter Buniat, https://github.com/hpbuniat (Duplicate background image rule) |
66 | | -1. Dino Chiesa, https://github.com/DinoChiesa (Windows Script Host CLI) |
67 | | -1. Tomasz Oponowicz, https://github.com/tomasz-oponowicz (XML format and CLI fixes) |
68 | | -1. Julien Kernec'h, https://github.com/parallel (Fixed a rule) |
69 | | -1. Cillian de Róiste, https://plus.google.com/116480676247600483573/posts (Node CLI fixes) |
70 | | -1. Damien Sennm, https://github.com/topaxi (README fixes) |
71 | | -1. Jonathan Barnett, http://twitter.com/indieisaconcept (JUnit formatter) |
72 | | -1. Zach Leatherman, http://www.zachleat.com/ (bug fixes) |
73 | | -1. Philip Walton, http://philipwalton.com (Rules fixes, bug fixes) |
74 | | -1. Jeff Beck, http://www.jeffbeck.info (Rules fixes, bug fixes) |
75 | | -1. Jay Merrifield, https://github.com/fracmak (Rules fixes) |
76 | | -1. Michael Mattiacci, http://mattiacci.com (Rules fixes) |
77 | | -1. Jonathan Klein, http://www.jonathanklein.net (Bulletproof font-face rule) |
78 | | -1. Shannon Moeller, http://shannonmoeller.com (Embedded rulesets) |
79 | | -1. Nick Schonning, https://github.com/nschonni (Contributing.md, grunt build) |
80 | | -1. Jared Wyles, https://github.com/jaredwy (Managing pull requests, endless advice) |
81 | | -1. Scott Gonzalez, https://github.com/scottgonzalez (JSON config) |
| 1 | +# This is a fork of the original CSSLint. |
| 2 | + |
| 3 | +You can get to the original |
| 4 | +* [on github](https://github.com/CSSLint/csslint) |
| 5 | +* [on npmjs](https://www.npmjs.com/package/csslint) |
| 6 | + |
| 7 | +## Changes |
| 8 | + |
| 9 | +### Core |
| 10 | +Changes to the CSSLint core in this fork |
| 11 | +* fix an bug that shows "undefined" evidence when the reported line shifts the array index beyond the boundary |
| 12 | +* allow options to be passed from the configuration file or command line to the `init` function of a rule |
| 13 | + |
| 14 | +Changes to the core have been tested with the node.js command line, but have not been tested with any other environments. |
| 15 | + |
| 16 | +### Rules |
| 17 | +Additional rules added in this fork |
| 18 | +* accessibility |
| 19 | +* background-color |
| 20 | +* color-contrast |
| 21 | +* lowercase |
| 22 | +* no-filter |
| 23 | +* no-tabs |
| 24 | +* obsolete-properties |
| 25 | +* rules-max |
| 26 | +* selector-pattern |
| 27 | +* transparent-color |
0 commit comments