I have some problems with getting analyze to produce warnings, this test is also failing: https://github.com/clojure/clojurescript/blob/master/src/test/clojure/cljs/analyzer_tests.clj#L31

Oh, it's the undeclared-var warning which doesn't work

@juhoteperi: I just pulled a fresh master and as you said, the test is failing! There is a standing issue for the other 2 failing tests: http://dev.clojure.org/jira/browse/CLJS-1349 but none for the no-warn you just discovered. Would you mind filing one?

@bensu: all-warn, yeah I'll do that

@juhoteperi: sorry, all-warn. great!

Created. I found the problem commit with bisect also.

@juhoteperi: thanks for going the extra mile with the bisect. Is this something you want to pursue or should I assign it to me?

@bensu: Feel free to take it. I looked into it quickly and couldn't see the cause straight away.

@juhoteperi: ok. I'll get it during the week so we can discuss the more interesting cljs-1367

@juhoteperi: I've been thinking about flags and analyzer.api, what would be the best to allow analyzer.api users to have some control over the flags, without exposing them directly since their impl might change.

one option is to pass an opts map as an interface to those flags, including the warning-handlers.

I'm mostly interested in using warning handlers together with cljs.build.api/build

So if the warning handlers were passed in as argument, they would need to be added elsewhere too

The most useful api for me would be if build (and others) returned useful value containing e.g. number of warnings

@juhoteperi: can you point me to the code that needs the number of warnings?

@bensu: https://github.com/adzerk-oss/boot-cljs/blob/next/src/adzerk/boot_cljs/impl.clj#L36-L52

If warning count is non-zero Boot can e.g. play sound notification

@juhoteperi: thanks, it makes sense.