On Mon, August 31, 2015 07:46, Niels Thykier wrote:
> On 2015-08-30 20:28, Axel Beckert wrote:
>> Hi,
>>
>> Niels Thykier wrote:
>>>> Moreover minified js is a security risk so removing tag is not really
>>>> an option
>>>
>>> The bug is not about removing the tag, it is about the amount of times
>>> it is emitted makes it difficult to spot other issues.
>>
>> Yep, wanted to argue, too. But Niels was quicker
>>
>>> This is not the only tag with this issue (improper stripping of static
>>> libraries also do this), and I think we need to look into a solution
>>> for
>>> this at a general level.
>>
>> What about a command-line and/or configuration file option which
>> restricts the amount of tags of the same type to be printed at all?
>>
>> Example option: --max-output-same-tag=10
>>
>> Regards, Axel
>>
>
> Yes. Though I would prefer lintian did something like this by default
> when stdout is a tty. Also, 10 instances of a single tag is quite a
> lot, I think 1-3 and a "+X more instances of this tag"-remark would be
> sufficient for most users.
That would be a nice feature and I think it makes sense as the default.
Nonetheless, the original issue could also be addressed by modifying the
test not to issue a tag on each of the potentially over 100 files it
encounters, but rather do something like:
if (any of the tinymce files found) {
issue tag ("tinymce found")
}
Cheers,
Thijs
