- New Rule: Mike Hopley suggested we add a rule that could suggest shorthand properties when all dimensions of
marginandpaddingwere provided as separate properties. That rule has been added. - Kasper Garnæs and Tomasz Oponowicz each contributed some cleanup code to the various XML formats the CLI supports, ensuring that proper escaping happened.
- Kasper also submitted the
checkstyle-xmloutput format for use with Checkstyle. - Cillian de Róiste contributed a fix for the Node.js CLI that ensures it will now handle absolute file paths correctly.
- Eric Wendelin implemented the
csslint-xmloutput format for compatibility with Jenkins Violations. - Julien Kernec’h added some missing CSS properties to the rule that checks for valid properties.
- I took a first pass at creating a developer guide for CSS Lint, explaining how the code is organized and how the build system works.
The complete changelog can be found at GitHub. If you’re using the Node.js version of CSS Lint, you can update your version via:
Please keep those submissions and issues coming. The GitHub issue tracker is the best way to get our attention. We’d also love to hear about how you’re integrating CSS Lint into your build system, feel free to drop us a line on the mailing list and tell us what you’ve been up to.
Disclaimer: Any viewpoints and opinions expressed in this article are those of Nicholas C. Zakas and do not, in any way, reflect those of my employer, my colleagues, Wrox Publishing, O'Reilly Publishing, or anyone else. I speak only for myself, not for them.
Both comments and pings are currently closed.
