[Plone-testing-team] CSSLint options.

Ramiro B. da Luz ramiroluz at gmail.com
Fri Oct 25 11:22:48 UTC 2013


On Thu, Oct 24, 2013 at 11:08 AM, Héctor Velarde
<hector.velarde at gmail.com> wrote:
> On 24-10-2013 10:51, Ramiro B. da Luz wrote:
>>
>> I removed because I figured out that the option to filter only errors is
>> other.
>> The --quiet option is used to avoid output for files that are OK.
>> To filter warnings for example you should use something like:
>> --errors=important
>>
>> You can use it in your configuration file, or we can add this to the
>> default
>> .csslintrc
>
>
> HV> no, you're confusing the goal of the options: by default, csslint will
> mark only CSS syntax errors as errors and all the other rules will be
> warinings; if you want csslint to raise an error if some of the rules are
> not fullfiled, then you use the --error option.
>
> for instance, --errors=important will make csslint rise an error if it finds
> an !important annotation in your CSS file; that should be configurable
> because that could be perfectly fine for most of the people.
>
> personally I always want to skip the rules I have on the default
> configuration because they don't make any sense, but I still have not
> decided for the other one; and some people will use csslint just to avoid
> syntax errors.
>
> then, the code you removed was just a workaround for a broken feature on
> csslint: --quiet.

I think we are confusing the options.
The quiet option is working. But it does not do what you want. It omit the
output of files that are ok, look at the example:

https://gist.github.com/ramiroluz/7153081

That function introduce a non configurable behavior to csslint usage. It filter
the output, but the user can't configure it and the user may expect an output
and will not figure out why the output is different from the command line.

I will try to find a way to configure csslint to do what you need, without that
function.

>
>
>> ok. But I have just one more commit ready to go, it change only the re of
>> the
>> csslint_error workaround.
>
>
> HV> be my guest, but remember: I want to have errors and warnings colored
> because is cool and I want csslint to honor all the options passed in the
> .csslintrc; I spent a lot of time checking this before and I don't want to
> have to do it again ;-)
>
>
>> Better than that I will made a beer for all. ;D
>
>
> HV> promisses in the dark ;-)
>



-- 
--
-- Ramiro Batista da Luz
-- ramiroluz at gmail.com
-- (41) 9173-2231
-- http://www.ramiroluz.eti.br
-- Programador || Câmara Municipal de Curitiba


More information about the Plone-testing-team mailing list