New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot generate internal documentation #2229
Comments
I think this bug/feature request is distinct from #2165. The difference is that I do not want to provide arguments to haddock but I do want haddock to be run on a different target than the one provided. |
I see! Yes, currently I don't think we have a way to do I'd almost want to have it be a default, but only if haddock made it clear they're for unexposed modules (doubtful) |
Hi guys. I really needed this for a project I'm working on, so I went ahead and took a swing at it. This is my first contribution to stack, so let me know if there is anything I missed in the way of completeness/style/policy. Thanks. |
Updated PR in #2598 |
This is a boolean argument which causes haddocks to be generated in the same manner as `cabal haddock --internal`, implemented by simply passing `--internal` to the `cabal haddock` invocation used to build the docs. It defaults to False.
Closed via #2598 |
Perhaps I did miss something, but it seems to me that generating internal documentation is not possible.
With cabal, I just use the following command line:
cabal haddock --internal
. Is there some similar switch for stack?The text was updated successfully, but these errors were encountered: