-
Notifications
You must be signed in to change notification settings - Fork 724
Add new-haddock support for --haddock-for-hackage
#4490
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
Merged
Merged
Changes from all commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
e14a9c4
Add support for `new-haddock --haddock-for-hackage`
noisegul 4f19f7d
Remove old commented placeholder
noisegul 38d057b
Move `instance Binary HaddockTarget` to module of class
noisegul cde8779
Add "for-hackage" flag to legacyPackageConfigFieldDescrs
noisegul 7366534
Move ForHackage to the end in PackageConfig
noisegul ff0e66a
Add for-hackage to unit-tests
noisegul 4bf497a
Merge remote-tracking branch 'upstream/master'
noisegul fa0d26e
Change arbitrary instance of HaddockTarget
noisegul 570c65b
Change default Flag of haddockForHackage to `NoFlag`
noisegul df53e50
Merge remote-tracking branch 'upstream/master'
noisegul a387779
Fix for-hackage rendering to distinguish NoFlag and default case.
ezyang 46fa1a2
Merge remote-tracking branch 'upstream/master'
noisegul c0a03ae
Merge remote-tracking branch 'upstream/master'
noisegul File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
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.
Fwiw, this looks somewhat inconsistent; we got a field named
ForHackagewhich would imply a Bool, but then this holds an enum which redundantly saysForHackage(orForDevelopment).Why isn't this simply a
Flag Bool?PS: To answer my own question, now I see that this has been inherited from
Distribution.Simple.Setup(haddockForHackage :: Flag HaddockTarget); so this PR just went along with the pre-existing design decision......and actually in #2852 this was still a
Flag Bool... it was 0975372 which lateron introduced theHaddockTargetdata type w/o addressing the introduced naming inconsistency...