Ignore compiler warnings about duck HOT 4 CLOSED

@koba04 The two options have different purposes, so consider them separately.
Option 1 should be done.
But why do you need option 2? I think that the straight forward way is to make it an error with Compiler option jscomp_error.

from duck.

@teppeis Thanks!

But why do you need option 2? I think that the straight forward way is to make it an error with Compiler option jscomp_error.

Ah, that's right.
I should change warning categories to ERROR if I want to do option 2.
https://github.com/google/closure-compiler/wiki/Warnings#warnings-categories

Let's discuss option 1.

I've written a patch for this.
But I doubt that there is a better approach to this.

This patch prints warnings to stderr using console.error.
I've tried to use logger for this, but I couldn't do that because, without nonTTY mode, logger output is collapsed by listr so we can't see the warnings.

from duck.

@koba04 There is a tricky way through logger. --printConfig uses this way.

1. input
2. store
3. output

But it's too complex and we need another solution.
I think it's enough that each command returns content and cli logic outputs it.

from duck.

I've pushed WIP to output warnings #296

from duck.