-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Add --out-dir flag for rustdoc #91310
Conversation
Yes, it should be stable, that's why I opened the FCP :)
What does rustc do when |
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.
Could you add a test using all three of these flags in different invocations and make sure it behaves properly? It may need to be a run-make test so you can check the generated files exist.
@jyn514 Tests added! Thanks for your review! 💚 💙 💜 💛 ❤️ |
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.
Could you also add a test for when --out-dir
and --output
are both passed? That one can just be a rustdoc-ui
test I think :)
Done. |
Can you squash the commits? This looks good to me after that, it just has to wait for the FCP to finish :) |
6631e45
to
0369ea1
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.
@hi-rustin Your "Add tests for options" commit also changes the rustdoc source code, which I found confusing when reviewing this. Could you please move those changes into your first commit and leave your second commit as just tests? Alternatively, could you squash into one commit?
5b2c973
to
f5f91ee
Compare
@camelid Done. |
Thank you @hi-rustin! One last comment: something seems to have happened to your commit message when you squashed, since it currently is this:
Could you fix it so the commit is
instead? You can use |
I think https://doc.rust-lang.org/nightly/rustdoc/command-line-arguments.html#-o--output-output-path needs to be updated as well. Perhaps with a |
I think it's ok to change the fragment - it will still go to the same page, just not the right header. |
I didn't find any results for |
f5f91ee
to
c8e21cd
Compare
Signed-off-by: hi-rustin <rustin.liu@gmail.com>
c8e21cd
to
03be3e2
Compare
Updated. |
FCP has finished. |
@bors r+ |
📌 Commit 03be3e2 has been approved by |
…askrgr Rollup of 6 pull requests Successful merges: - rust-lang#91127 (Add `<*{const|mut} T>::{to|from}_bits`) - rust-lang#91310 (Add --out-dir flag for rustdoc) - rust-lang#91373 (Add needs-unwind to tests that depend on panicking) - rust-lang#91426 (Make IdFunctor::try_map_id panic-safe) - rust-lang#91515 (Add rsplit_array variants to slices and arrays) - rust-lang#91553 (socket ancillary data implementation for dragonflybsd.) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
part of #91260
Add --out-dir flag for rustdoc and change the
-o
option to point to out-dir.I'm not quite sure if it should be stable, also I'm not sure if this parameter priority is appropriate? Or should I just refuse to pass both parameters at the same time?
r? @jyn514