-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
Make x doc --open
work on every book
#108394
Conversation
r? @ozkanonur (rustbot has picked a reviewer for you, use r? to override) |
This comment has been minimized.
This comment has been minimized.
Seems we have an error in CI pipeline @rustbot author |
@bors review |
@rustbot review |
When |
That is the current behavior for the books that already support |
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.
That is the current behavior for the books that already support --open.
LGTM then, sorry for the noise.
I think it would be nicer to open the doc
once for all after the compilation. I will check what I can do for this.
@bors r+ rollup |
Rollup of 7 pull requests Successful merges: - rust-lang#108143 (rustdoc: search by macro when query ends with `!`) - rust-lang#108394 (Make `x doc --open` work on every book) - rust-lang#108427 (Recover from for-else and while-else) - rust-lang#108462 (Fix `VecDeque::append` capacity overflow for ZSTs) - rust-lang#108568 (Make associated_item_def_ids for traits use an unstable option to also return associated types for RPITITs) - rust-lang#108604 (Add regression test for rust-lang#107280) - rust-lang#108605 (Add regression test for rust-lang#105821) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
Before this PR, the
--open
flag had to be configured explicitly for every book, and most of them didn't configure it, resulting in the flag silently failing in all but two books.In this PR, the code to check for the
--open
flag is in the underlyingRustbookSrc
step rather than all the individual steps. This is done by passing the parent step as a field ofRustbookSrc
, so that we can check for the correct step inmaybe_open_in_browser
.This was part of a larger change that in the end wasn't worth it. Still, I think it could be useful as-is.