-
Notifications
You must be signed in to change notification settings - Fork 110
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
Justification of html_root_url is missing nuance #229
Comments
Note that this has nothing to do with docs.rs, docs.rs passes |
I'm pretty sure this guideline was created in a time where not specifying |
Oh hmm - I think when it was originally written rustdoc didn't support Should I make a PR removing the recommendation? |
Oh heh - it has a comment pointing to rust-lang/rust#42301, which I closed as wontfix a few days ago. |
I'm not even sure docs.rs was even around back then. But I can't remember. :) |
For what it's worth I'm fairly certain most crates (including all of mine) don't use this attribute, and I have never had an issue with links not working exactly as expected. |
rust-lang/api-guidelines#229 suggests it's not necessary.
Sounds like we should remove the recommendation then! It's a bit of a footgun that we don't need anymore. |
Actually, since we have just been talking about the way we make decisions on this repo I should try actually follow what we set out and kick off an FCP! |
@rfcbot fcp merge I propose we remove the guideline recommending |
Guess I'd better go find out why @rfcbot doesn't want to hang out here |
Team member @KodrAus has proposed to merge this. The next step is review by the rest of the tagged team members: No concerns currently listed. Once a majority of reviewers approve (and at most 2 approvals are outstanding), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up! See this document for info about what commands tagged team members can give me. |
👀 @rfcbot unchecked @BurntSushi 's checkbox |
Weird. I just checked it again. |
Oh wow... It did work 😮 |
Also note there was some lengthy discussion in #230 about this and its implications for non-Cargo build systems. |
Given I work solely in Stable, effectively no... but I've watched that issue now (I missed the reference in the OP before). |
🔔 This is now entering its final comment period, as per the review above. 🔔 psst @KodrAus, I wasn't able to add the |
The final comment period, with a disposition to merge, as per the review above, is now complete. As the automated representative of the governance process, I would like to thank the author for their work and everyone else who contributed. The RFC will be merged soon. psst @KodrAus, I wasn't able to add the |
rust-lang/api-guidelines#229 - while the issue is still open, the RFC has passed so will be merged in at some point.
As a side-note: that is why I created the version-sync crate. It makes it trivial to add an integration test which will fail if you forget to update the |
#230 was merged, this can be closed. |
This is no longer recommended: see rust-lang/api-guidelines#229.
This is no longer recommended: see rust-lang/api-guidelines#229.
This is no longer recommended: see rust-lang/api-guidelines#229.
It's no longer recommended. See rust-lang/api-guidelines#229
It's no longer recommended. See rust-lang/api-guidelines#229
cc #75, @dtolnay
From rust-cli/env_logger#185:
The scenario where this goes wrong (assuming you're the author of
env_logger
and not usinghtml_root_url
) is:downstream
crate usesenv_logger
as a dependencydownstream
re-exports or in some other way links toenv_logger
downstream
builds documentation locally withcargo doc --no-deps
(without--extern-html-root-url
, because in practice no one but docs.rs does that).Then the links to
env_logger
will be broken. But there's a simple fix and the fix is to remove--no-deps
. Is this really so common that it's worth recommending that library authors usehtml_root_url
?Note that I'm hoping to fix this properly in cargo instead: rust-lang/cargo#8296
The text was updated successfully, but these errors were encountered: