search

jamesallardice / jslint-error-explanations

:memo: Explanations of all the (sometimes cryptic) error messages thrown by JSLint and JSHint
http://linterrors.com
293 stars 35 forks source link

Remove CSS-linting-related error messages? #3

Closed webignition closed 11 years ago

webignition commented 11 years ago

JSLint has an experimental feature to lint CSS files. This mostly covers checking for whitespace-related matters but does also cover some CSS-specific issues that are wholly not relevant to JavaScript.

The list of pages needed includes all errors that could potentially be raised by JSLint, including some that are not relevant to the linting of JavaScript.

As jslinterrors.com is "designed to help you improve your JavaScript", should the focus of the site be purely on JavaScript-related improvement and if so should the CSS-only errors be removed from the list of pages needed?

I suppose this question could be generalised as: should the site cover all possible errors that can be raised by JSLint (and JSHint), or should the site instead focus only on the subset of errors that relate to JavaScript?

webignition commented 11 years ago

Note: I tried to label this as 'question' as it's not a bug, didn't manage to.

jamesallardice commented 11 years ago

Thanks for the question. I'm still undecided on this. I've purposefully avoided writing any pages on the CSS related errors so far because as you say, the site is geared towards JavaScript. It is "JS"Lint after all... I'm not sure why it even handles CSS!

I'm open to the thoughts of the community on this one... if people would find it useful, I'll eventually include all of the CSS messages too. Perhaps they could belong in a separate area/have a separate label to filter them on. It will definitely require modifications to the interactive linting tool.

So, everybody:

Should the site cover all possible errors that can be raised by JSLint (and JSHint), or should the site instead focus only on the subset of errors that relate to JavaScript?

rabchev commented 11 years ago

It makes sense to me to have all three, JavaScript, HTML and CSS, covered as they usually go together. I rarely do frontend development, but occasionally I have to and I find it quite annoying that JSLint is not as good on the last two as on JavaScript.

For instance, on a partial HTML template I get this massage: “Expected ‘html’ and instead saw ‘div’”. How do I turn off JSLint features in HTML?

jamesallardice commented 11 years ago

This just became a bit less of an issue... HTML, CSS and ADsafe parsing were removed from JSLint in a recent commit. I may still add articles for them at some point, just for the sake of completeness, but it can be really low priority now.

webignition commented 11 years ago

That makes perfect sense. I'll close this now.