Open UnkindPartition opened 8 years ago
Duplicate of https://github.com/commercialhaskell/stack/issues/729 , I agree it should be fixed. PRs appreciated!
I've seen #729, but I think it's mostly unrelated, albeit similar. It talks about generating haddocks for the executable code. I'm talking about generating haddocks for libraries that are dependencies of executables, tests, and benchmarks.
In particular, I feel like the dependencies for all components should be treated uniformly by stack haddock
. I shouldn't have to say --executables
to generate the docs for executable deps. Also, I doubt there are going to be similar switches for test and benchmark code, but having the docs for their dependencies is just as important.
I see! Thanks for the clarification @feuerbach !
Just ran into this, and wanted to add in case anyone else is googling this, that this means stack hoogle
also won't work for e.g. hspec functions.
General summary/comments (optional)
stack haddock
generates the documentation for the dependencies of the library component, but not of the executable or test components.Steps to reproduce
stack haddock
Expected
If I go to the doc index (
.stack-work/install/x86_64-linux/lts-7.0/8.0.1/doc/all/index.html
), I expect to see the executables and test suite dependencies docs.Actual
They're not there.
Stack version
Method of installation
Built from git.