Uh oh!
There was an error while loading. Please reload this page.
Set --extend-css stable - #41700
Conversation
alexcrichton
commented
May 2, 2017
steveklabnik
commented
May 3, 2017
Let's talk about this at a doc meeting. |
steveklabnik
commented
May 11, 2017
We decided at the docs meeting that since rustdoc is currently in-progress moving under devtools, we're gonna hold off until then. |
GuillaumeGomez
commented
May 11, 2017
😿 |
Mark-Simulacrum
commented
May 11, 2017
@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... |
GuillaumeGomez
commented
May 12, 2017
A new team should be created (soon or not, not sure about this), and in this team, a subteam will officially handle rustdoc changes. |
steveklabnik
commented
May 15, 2017
@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. |
carols10cents
commented
May 22, 2017
@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) |
killercup
commented
May 22, 2017
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 |
nrc
commented
May 22, 2017
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 |
GuillaumeGomez
commented
May 23, 2017
Ok, will add it as well. |
GuillaumeGomez
commented
May 23, 2017
Updated. Is the help message good enough? |
There was a problem hiding this comment.
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.
No problem, it avoids further fixes.
df30708 to
b4d594fComparekillercup
commented
May 24, 2017
Thanks. The description looks good! (Maybe drop the "to" at the beginning but that really doesn't matter 😅) |
GuillaumeGomez
commented
May 24, 2017
@bors: r=killercup |
bors
commented
May 24, 2017
📌 Commit b4d594f has been approved by |
bors
commented
May 24, 2017
⌛ Testing commit b4d594f with merge bb8b661... |
steveklabnik
commented
May 24, 2017
(For posterity, @QuietMisdreavus and I both signed off on this as well) |
bors
commented
May 24, 2017
💔 Test failed - status-appveyor |
Mark-Simulacrum
commented
May 24, 2017
@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
bors
commented
May 25, 2017
⌛ Testing commit b4d594f with merge 7f3ed6c... |
Mark-Simulacrum
commented
May 25, 2017
There's very little chance of this succeeding on its own due to appveyor slowness. @bors retry |
bors
commented
May 25, 2017
Set --extend-css stable I think it's now time to set this option stable. r? @rust-lang/docs
bors
commented
May 25, 2017
☀️ Test successful - status-appveyor, status-travis |
I think it's now time to set this option stable.
r? @rust-lang/docs