-
Notifications
You must be signed in to change notification settings - Fork 710
[#5503] Add filterHaddockFlags for new-haddock #5569
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
Conversation
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.
Great! Thanks @chshersh! And sorry for the oversight!
@alexbiehl the problem appears to be (haven't investigated enough to be sure) that @chshersh I'm afraid, we need to do a bit more here; we need to e.g. extend the arg filtering to detect this case somehow |
@alexbiehl @chshersh take a look at this here cabal/Cabal/Distribution/Simple.hs Line 708 in 0c97920
(IOW, this was an oversight of #5226) I'm afraid we've been looking at the wrong place to fix this... |
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.
different fix needed:
- try using
readHookWithArgs
forpreHaddock
- (maybe) write a regression test-case
@chshersh maybe open a separate PR; I'd like to leave this PR open as it may still have merit on its own for consistency reasons
@hvr Sure, no problems. I will do the work in separate PR 👌 |
Please include the following checklist in your PR:
[ci skip]
is used to avoid triggering the build bots.I've tried to add additional logic suggested by the issue. But I still see the error: