Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
`stack haddock` should always return location of index.html #781
I propose that
It can be inconvenient tracking down the documentation produced by
When the command produces documentation, the last line of the output is
The last line would be useful when there is no new documentation generated.
Steps to reproduce:
The second run produces something like
The command prints nothing.
Here is the
Here is the command I ran with
changed the title from
`stack haddock` should always return location of index.html (Enhancement)
`stack haddock` should always return location of index.html
Aug 13, 2015
Yeah, that makes sense. I wonder if it should show the locations of all three indices (stack version 0.1.3.1 also generates an index that includes all dependencies, as well as one for all snapshot packages ever installed). A pull request would certainly be welcome.
Along with always outputting the filepath, it would be good to ensure that this, and similar outputs, always come at the end of the build. For example, I'd be quite surprised if
referenced this issue
Dec 18, 2016
I can't see the resolved behavior - neither in stack 1.4 nor stack 1.5. My command will dump some haddock warnings and nothing more.
I don't know if it fails - maybe that's why it doesn't write any output, but if so it should say that instead of being silent.
For me on stack 1.5/Win10:
So as it is I can't reproduce your problem. If you are sure the Paths don't show up while haddock/build does succeed please post OS, Console Log and a project on which it happens so I can take a look.
No, the paths don't show up when haddock fails, but whether haddock succeeds or not is not apparent. I think either the url should be printed anyways, or some "last message" saying why it's not provided (the haddock build failed) should be printed.
When would printing the expected URL after a failed haddock call be useful?
Personally I don't see much value in printing it in any of these cases.
Improving the feedback to make it clearer that haddock failed is a good idea but doesn't really match this issue imo so if you want to make that feature request it would be better to open a new Issue.
Also for me