Error attempting to use lein-doo 0.1.7

[ricardojmendez]

Get the following assertion error when attempting to run lein with-profile test doo phantom with plugin 0.1.7:

(not (and (default? cli-alias) (not (contains? alias-map :default))))

Version 0.1.6 of the plugin works just fine. Configuration is simply :doo {:build "test"}

[MatthewDarling]

Skimming the responsible code a bit, it seems like that assertion is meant to catch not specifying an environment (lein doo, without setting a default) or an invalid environment (lein doo foo).

phantom should be a valid environment alias, though.

Do you have an example repository that shows this behaviour?

[miikka]

This is still an issue with Doo 0.1.8. There's an assertion that has helpful text, but it unhelpfully also prints a stacktrace. The stacktrace should be suspended, and in general, assertions shouldn't be used for validating the command-line arguments. Assertion failures should indicate a bug in the program and the user not knowing the right arguments is not a bug.

doo/plugin/src/leiningen/doo.clj

Lines 101 to 111 in fe0e7d4

	(assert (not (and (default? cli-alias) (not (contains? alias-map :default))))
	"\n
	To call lein doo without a js-env you need a :default :alias in
	your project.clj and a default build. For example:
	{:doo {:build {:source-paths [\"src\" \"test\"]}
	:alias {:default [:firefox]}}}
	then you can simply use
	lein doo\n")

[bensu]

That sounds like a sensible rule. figwheel has some good error reporting, maybe we should steal it.