-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Set --extend-css stable #41700
Set --extend-css stable #41700
Conversation
Let's talk about this at a doc meeting. |
We decided at the docs meeting that since rustdoc is currently in-progress moving under devtools, we're gonna hold off until then. |
😿 |
@steveklabnik Could you elaborate about what "moving under devtools" means? I don't think I've heard of this yet, though I may have missed something... |
A new team should be created (soon or not, not sure about this), and in this team, a subteam will officially handle rustdoc changes. |
@Mark-Simulacrum there's some restructuring of some parts of the teams going on, similar to how the new infrastructure team was spun up. Rustdoc's governance is part of this. |
@rust-lang/dev-tools exists now! ping all of yinz! |
ono i have 'sponsibilities now (I'm a tool peer so I don't think I have to sign off on this, but, in case, 👍 from me) |
With great power comes great opportunity to bikeshed! Okay, let me warm up with: I'd prefer to have CSS written in uppercase in the description. Also, I'm not sure if this actually merits the I'm 👍 on the general idea to stabilize the |
We discussed this at the dev-tools meeting today. We were in favour of stabilising. There is a concern that since we do not want to freeze the HTML output by rustdoc, then user css could have different effects from version to version and this might make it more difficult to change rustdoc. However, there is basically no solution to this other than not stabilising the option. So, we think we should accept this PR (r+) on the condition that an extra line of documentation is added to the |
Ok, will add it as well. |
Updated. Is the help message good enough? |
src/librustdoc/lib.rs
Outdated
@@ -162,8 +162,9 @@ pub fn opts() -> Vec<RustcOptGroup> { | |||
"URL to send code snippets to", "URL")), | |||
stable(optflag("", "markdown-no-toc", "don't include table of contents")), | |||
stable(optopt("e", "extend-css", | |||
"to redefine some css rules with a given file to generate doc with your \ | |||
own theme", "PATH")), | |||
"To redefine some css rules with a given file to generate doc with your \ |
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.
s/redefine/add
s/css/CSS
s/doc/the documentation
I'm not sure about the "add", but I think "redefine" sends the wrong message. You are not changing existing CSS rules, just adding more rules, that may be more specific (because of specificity) and thus appear like they replaced the default rules.
In addition to that it is also totally possible to add new rules for that .fancy-table
you used in your docs.
(Sorry to continue do nitpick on this)
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.
No problem, it avoids further fixes.
df30708
to
b4d594f
Compare
Thanks. The description looks good! (Maybe drop the "to" at the beginning but that really doesn't matter 😅) |
@bors: r=killercup |
📌 Commit b4d594f has been approved by |
⌛ Testing commit b4d594f with merge bb8b661... |
(For posterity, @QuietMisdreavus and I both signed off on this as well) |
💔 Test failed - status-appveyor |
@bors retry
|
…=killercup Set --extend-css stable I think it's now time to set this option stable. r? @rust-lang/docs
…=killercup Set --extend-css stable I think it's now time to set this option stable. r? @rust-lang/docs
⌛ Testing commit b4d594f with merge 7f3ed6c... |
There's very little chance of this succeeding on its own due to appveyor slowness. @bors retry |
Set --extend-css stable I think it's now time to set this option stable. r? @rust-lang/docs
☀️ Test successful - status-appveyor, status-travis |
I think it's now time to set this option stable.
r? @rust-lang/docs