-
Notifications
You must be signed in to change notification settings - Fork 696
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
Fix #5210 Don't refer to index.html
when Haddock will not create it
#9332
Conversation
Any chance for a test? Changelog would be nice too. |
As requested, I've add something to I can't think of how to test for the original mistake. |
There's a |
Thanks! The explanation about changelogs is referenced in the PR template. |
@geekosaur, @ulysses4ever apologies on ChangeLog. I've now read the instructions, and tried again. |
For testing: could you create a copy of
to
and replace the last line in the same file ( I may be missing some details but high-level this is the way to go, I think. To test is locally you may need to dive into https://github.com/haskell/cabal/blob/master/cabal-testsuite/README.md Most importantly, |
@ulysses4ever, I have added a test but my attempts to test the test locally came to naught, because |
d4d1f03
to
defd6c7
Compare
Thank you for willing to give it a go, and I'm sorry it doesn't go through yet.
|
Sorry, didn't see the edits until now (better send new comments — for visibility). Yes, .out will need to be adjusted. Usually it's done by calling the test binary with --accept but if you can't run it locally, this may be a problem... |
@ulysses4ever, I finally arrived at a test that has passed the CI. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Terrific, thank you! Apologies for all the pain due to the test suite, but tests is the only way to assure sanity in the future..
Haddock documents that it will not create
index.html
if option--use-contents
or option--use-index
is passed to it. See: https://haskell-haddock.readthedocs.io/en/latest/invoking.html#cmdoption-use-contentsHowever, that is not reflected in the existing logic for
result
inDistribution.Simple.Haddock.renderArgs
, resulting in the behaviour complained about in issue #5210. This pull request fixes that.