Open sjakobi opened 7 years ago
Motivated by this SO question I just updated the documentation for the build options.
build
Here are a few inconsistencies that I noticed:
In the yaml config we have test-arguments, haddock-arguments but benchmark-opts.
test-arguments
haddock-arguments
benchmark-opts
We have test and test-X, haddock and haddock-X, but bench and benchmark-X.
test
test-X
haddock
haddock-X
bench
benchmark-X
--test-arguments
test-arguments: additional-args
--haddock-arguments
haddock-arguments: haddock-args
--benchmark-arguments
benchmark-opts: benchmark-arguments
haddock-deps, open-haddocks and haddock-internal should be inside the haddock-arguments block
haddock-deps
open-haddocks
haddock-internal
test additional-args and haddock-arguments each take a list of strings, while benchmark-arguments takes a single string (I didn't check the CLI)
additional-args
benchmark-arguments
Related (possibly duplicate?): #652
Another one that I just ran into: we have --ghc-options to pass arguments to GHC, but --{test,haddock,benchmark}-arguments.
--ghc-options
--{test,haddock,benchmark}-arguments
Motivated by this SO question I just updated the documentation for the
build
options.Here are a few inconsistencies that I noticed:
In the yaml config we have
test-arguments
,haddock-arguments
butbenchmark-opts
.We have
test
andtest-X
,haddock
andhaddock-X
, butbench
andbenchmark-X
.--test-arguments
->test-arguments: additional-args
--haddock-arguments
->haddock-arguments: haddock-args
--benchmark-arguments
->benchmark-opts: benchmark-arguments
haddock-deps
,open-haddocks
andhaddock-internal
should be inside thehaddock-arguments
blocktest
additional-args
andhaddock-arguments
each take a list of strings, whilebenchmark-arguments
takes a single string (I didn't check the CLI)