-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Use double quote for rustdoc html #76096
Conversation
I would prefer we standardize on using double quote everywhere because that's what pulldown-cmark uses. |
@ollie27 But that require escaping everywhere, or maybe we could do |
I don't think that's too big of a deal. Unfortunately |
6cad56f
to
31ec0ce
Compare
Double quotes usage is less than single quote right now, 85 vs 124 lines. |
☔ The latest upstream changes (presumably #76186) made this pull request unmergeable. Please resolve the merge conflicts. |
Ping from triage |
@pickfire any updates on this pr? |
I was waiting for reviewer to say if we should proceed with this, if it is good then I will go and resolve the conflicts and fix the build, otherwise can just close it. Thanks for the ping. |
Triage: It seems this PR needs decision here. @GuillaumeGomez @jyn514 |
@pickfire if you use double quotes like suggested by ollie (#76096 (comment)) and revert the change to |
Oh wait, you already did that 😆 this looks fine after a rebase then. |
0ee0d7d
to
29519b7
Compare
☔ The latest upstream changes (presumably #77926) made this pull request unmergeable. Please resolve the merge conflicts. Note that reviewers usually do not review pull requests until merge conflicts are resolved! Once you resolve the conflicts, you should change the labels applied by bors to indicate that your PR is ready for review. Post this as a comment to change the labels:
|
@jyn514 I rebased but now there is a merge conflict again. |
@pickfire please ping me after you rebase, I don't know to review unless you say something. Sorry you have to rebase again. |
@bors p=1 This PR bitrots quickly. |
29519b7
to
fe22442
Compare
@jyn514 ping |
@pickfire you need to run x.py fmt:
|
I won't be running |
fe22442
to
11f5e0b
Compare
@pickfire x.py fmt only takes a few seconds to run (at most a few minutes if you have to compile bootstrap first). But if it works, it works. |
I already took a few minutes to compile bootstrap. Oh no, merge conflicts! T_T |
☔ The latest upstream changes (presumably #78001) made this pull request unmergeable. Please resolve the merge conflicts. Note that reviewers usually do not review pull requests until merge conflicts are resolved! Once you resolve the conflicts, you should change the labels applied by bors to indicate that your PR is ready for review. Post this as a comment to change the labels:
|
11f5e0b
to
f49b82c
Compare
@jyn514 pong |
@bors delegate=pickfire Please wait to approve until CI passes, and use |
✌️ @pickfire can now approve this pull request |
f49b82c
to
dc80b6a
Compare
dc80b6a
to
2ce11af
Compare
Maybe you made a typo somewhere? |
Co-authored-by: Oliver Middleton <[email protected]>
@ollie27 Thanks r=jyn514 |
@bors r=jyn514 |
📌 Commit e96ca1b has been approved by |
☀️ Test successful - checks-actions, checks-azure |
r? @GuillaumeGomez
Feels scary without escaping stuff when I looked at the code, probably susceptible to XSS.
Follow up of #75842