-
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
haddock-project fixes #8919
haddock-project fixes #8919
Conversation
4ad4ab9
to
5e24585
Compare
@Kleidukos do you know a package published on |
haskell/hackage-server#1119 is still open... |
The CI failure seem to be expected at this point? I've tentatively marked it for backport to 3.10 branch, since it fixes (semi-) regressions and it's not a huge risky PR. |
It's unexpected. I'll try to reproduce it locally. |
Looking closer, these CI failures are expected. I changed the log output of the
|
5e24585
to
076f70c
Compare
@Mikolaj do you want me to create a PR against the |
No, thank you. Mergify will do this automatically for us and I sincerely hope there won't be any conflicts. |
nice :), there shouldn't be any. |
dbebb68
to
53cc424
Compare
e0b461a
to
ec1027a
Compare
@coot I don't even know if it's allowed. Hackage doesn't seem to support it? |
It is but a comment there |
ec1027a
to
4d2e7bd
Compare
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.
Good for me!
I pushed one more commit to fix #8958. |
@coot could you add a test that ensures that dependencies are handled correctly? |
yes, I am planning to do that. |
ce698df
to
24c4c07
Compare
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.
After a quick look, LGTM, but a more thorough review would be welcome.
Whether we backport is up to @Kleidukos.
@Mergifyio backport 3.10 |
✅ Backports have been created
|
@julialongtin would you like to perform the QA procedure on this PR? :) |
@coot you reached 2 approvals now, so you can put the |
Thanks @ulysses4ever, @Kleidukos & @Mikolaj for cooperation. |
Thank you, @coot. That's a long struggle, but many people waited years for these features and here they are finally, more and more usable. |
Shouldn't mergify do its job by now? |
I think you commented before the full 48 hours passed. And now the timer is probably reset. But let's fix it. |
@Mergifyio refresh |
✅ Pull request refreshed |
It says "Unable to update: user coot is unknown. Please make sure coot has logged in Mergify dashboard." What was that about? |
In the failure like this (" ❌ Queue: Embarked in merge train"), rebase is usually the way to go (Mergify fails to rebase a PR from a non-admin user on its own). "Refresh" works better when the bot thinks that some checks are not satisfied. |
@mergify rebase |
This patch fixes a bug where a sublibrary overwrites a library directory. This leads to overwriting `*.haddock` files, which results in missing entries in various indexes (e.g. the html index, quicksearch).
This patch makes `haddock-project` use `--local` option by default. Since its the default, it is removed. Also `--gen-index`, `--gen-contents`, `--hyperlinked-source` and `--quickjump` are removed since they are always turned on. Added a haddock-project test.
`haddock-project` command need to build the project so that haddocks of the dependencies are available in the store. Fixes #8958.
✅ Branch has been successfully rebased |
d74a550
to
2c597e8
Compare
This PR includes three commits which later
haddock-project
command:UnitId
instead of package namehaddock-project
options (fixes Theindex.html
that are supposed to be produced bycabal haddock-project
are not here. #8843)haddock-project --local
does not copy non-boot dependencies to output dir #8958)QA Notes:
cabal haddock-project
Running
cabal haddock-project
should create documentation folder./haddocks
which contains:./haddocks/<package-name>
folder for every dependency of the project; in particular./haddocks/<package-name>/<package-name>.haddock
should be present;./haddocks/index.html
;./haddocks/quick-jump.min.js
When serving the
./haddocks
folder withhttp
server the index page should list all the local packages. Using quick jump from the index page should allow to find any identifier found in any of the local packages, when viewing documentation of one of them quick jump should allow to jump to any identifier of that package. All entities should be linked, e.g. if you findIO
in the documentation, it should lead you to base documentation ofIO
.cabal haddock-project --hackage
Running
cabal haddock-project --hackage
should create documentation folder./haddocks
which only contains documentation of local packages. Identifiers from dependencies should be linked tohackage
.Please include the following checklist in your PR:
Bonus points for added automated tests!