-
Notifications
You must be signed in to change notification settings - Fork 841
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
No package names in haddock index #2886
Comments
Hmm, not sure why that would be, considering we are essentially using stack/src/Stack/Build/Execute.hs Line 1306 in 1020a2f
,"--haddock-options=--package-name=" ++ packageNameString (packageName package) ++ " --package-version=" ++ versionString (packageVersion package) But no difference in the index :/ |
…ents. It turned out that Haddock expects to see packages with those names in the GHC package DB. Pointing Haddock to the local and snapshot DBs resolved the issue.
…ents. It turned out that Haddock expects to see packages with those names in the GHC package DB, and omits the names otherwise. Pointing Haddock to the local and snapshot DBs resolved the issue.
…ents. It turned out that Haddock expects to see packages with those names in the GHC package DB, and omits the names otherwise. Pointing Haddock to the local and snapshot DBs resolved the issue.
It turned out that Haddock expects to see packages with those names in the GHC package DB, and omits the names otherwise. Pointing Haddock to the local and snapshot DBs resolved the issue.
PR #3226 has been merged. |
Thanks a lot! |
Sure, thanks goes to @judah for figuring out the problem and writing the patch! |
The package index generated by
stack haddock
does not contain the package names. The package names seem to be present for the packages distributed with ghc but not for the packages installed with stack.Here's a screenshot of my
~/.stack/snapshots/x86_64-linux/lts-7.0/8.0.1/doc/index.html
. Notice the difference between, say,BasicTypes
(distributed with ghc) andBio.Core
(from thebiocore
package, installed with stack from hackage).It's been a while since I looked at haddock, but my guess is that it has a command line option to specify the package name that stack does not pass.
The practical significance of this is that it makes it harder to search the index page, especially for packages that are named differently from their modules.
Stack version
Method of installation
from git master
The text was updated successfully, but these errors were encountered: