-
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
Reenable linkchecker for books #39976
Reenable linkchecker for books #39976
Conversation
This reverts commit 7f1d1c6. The original commit was created because mdBook and rustdoc had different generation algorithms for header links; now with rust-lang#39966 , the algorithms are the same. So let's undo this change. ... when I came across this problem, I said "eh, this isn't fun, but it doesn't take that long." I probably should have just actually taken the time to fix upstream, given that they were amenable. Oh well!
@steveklabnik: no appropriate reviewer found, use r? to override |
r? @frewsxcv |
6258ae1
to
5a42c59
Compare
Travis:
|
r=me with lockfile thing sorted out |
hrm, I don't understand why it's doing that; tidy passes for me locally. EDIT: Oh, I forgot to commit the lockfile, dunno why... |
5a42c59
to
f5951af
Compare
@bors: r=frewsxcv |
📌 Commit f5951af has been approved by |
Previously, mdBook used JavaScript to add header links, so we skipped checking the book. As of rust-lang#39966, it no longer does, so we can start checking again. There is a twist, though: it uses name instead of id, so let's test for both. They're both valid links anyway, so it's good to have the checker check anyway.
This brings in a needed bugfix.
f5951af
to
010a28d
Compare
@bors: r=frewsxcv (I left in a warning by accident) |
📌 Commit 010a28d has been approved by |
Why have you used the |
That is what mdbook has always used for these links. |
Is there a good reason for that? I'm pretty sure |
You should file a bug on mdbook about it. |
…ker, r=frewsxcv Reenable linkchecker for books In some senses, this is a revert of rust-lang@cacb3bc#diff-b64563d143f859565c8357a28ef81101R212; we disabled linkchecker for the book because the links were added by JavaScript. Now, that's fixed upstream, and so we can re-enable the checker. This also involves two other fixes: we have to check for `name`s as well as `id`s for links, and the linking algorithm of mdBook changed to the same as rustdoc's, so we change some links back. ~~~This isn't quite ready yet; it's [depending on a PR of mine to mdBook](https://github.com/azerupi/mdBook/pull/209). After that's released, this should be the last of these kinds of shenanigans~~~ 😄 This is good to go 😄
In some senses, this is a revert of cacb3bc#diff-b64563d143f859565c8357a28ef81101R212; we disabled linkchecker for the book because the links were added by JavaScript. Now, that's fixed upstream, and so we can re-enable the checker.
This also involves two other fixes: we have to check for
name
s as well asid
s for links, and the linking algorithm of mdBook changed to the same as rustdoc's, so we change some links back.