There is lesslint for running on less code. It uses CSSLint under the hood. I
don’t think CSSLint can be run on less code.
> On Nov 23, 2014, at 7:38 PM, Jon Robson wrote:
>
> Can CSSLint be run on less code though, or will we have to generate
> load.php urls and run it there?
>
> is there any
Can CSSLint be run on less code though, or will we have to generate
load.php urls and run it there?
is there any advantage to using lesslint / any reason we wouldn't use it?
On Sat, Nov 22, 2014 at 5:12 AM, Bahodir Mansurov
wrote:
> Here are our [1] LESS code conventions. Basically, CSSLint doe
Here are our [1] LESS code conventions. Basically, CSSLint doesn’t support any
of our existing conventions. It’s more concerned about errors, compatibility,
and performance. Our rules are mainly about syntax. We could write (in
JavaScript) CSSLint rules to support our current code conventions th
CSS is a beast and any help is going to be useful.
As Jon said, we probably need a longer spike/task to see if any other teams
are doing CSS linting and there are already conventions we can use, and to
determine what validation rules we want to use.
El 21/11/2014 2:53, "Jon Robson" escribió:
> W
Which rules would MobileFrontend be able to use from the start?
Which rules might be controversial to adopt?
On Fri, Nov 21, 2014 at 9:00 AM, Bahodir Mansurov
wrote:
> After reading benefits of CSSLint there is no doubt in my mind that we
> should use it. Here [1] are some of the benefits. They
After reading benefits of CSSLint there is no doubt in my mind that we should
use it. Here [1] are some of the benefits. They range from possible errors to
compatibility to performance, etc. With grunt we can use grunt-lesslint [2],
which employs CSSLint under the hood so we can also tweak it us
