Uh oh!
There was an error while loading. Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork 34.3k
http2: Correcting the heading format#22262
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
Uh oh!
There was an error while loading. Please reload this page.
Conversation
antsmartian commented Aug 11, 2018 • edited
Loading Uh oh!
There was an error while loading. Please reload this page.
edited
Uh oh!
There was an error while loading. Please reload this page.
trivikr commented Aug 11, 2018
Trott commented Aug 11, 2018
@vsemozhetbyt@rubys (just to get the eyes of the people most familiar with our current markdown processing quirks and bugs) |
vsemozhetbyt commented Aug 11, 2018
This is indeed a regression in the new toolchain, but it should be fixed eventually in the #22140 (checked and confirmed in #22140 (comment)) |
vsemozhetbyt commented Aug 11, 2018 • edited
Loading Uh oh!
There was an error while loading. Please reload this page.
edited
Uh oh!
There was an error while loading. Please reload this page.
We usually do not use backticks in API headings (when all the heading needs to be wrapped in backticks) and do use them for code entities in common headings. |
gdams commented Aug 14, 2018
@antsmartian can you please resolve the conflicts? |
doc/api/http2.md Outdated
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.
Is moving the heading intentional? It seems the next paragraph is out of topic now?
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.
Nope, I tried to resolve conflicts via browser and things didn't went well.
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.
I will squash my commits and update the PR.
c3565d7 to ae7922fCompare80cf121 to 6889fc1Compareantsmartian commented Aug 14, 2018
@vsemozhetbyt Now it should be good to go. cc @gdams fixed the conflicts. |
gdams commented Aug 14, 2018
gdams commented Aug 14, 2018
landed in: fc84666 |
PR-URL: #22262 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Trivikram Kamat <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: George Adams <[email protected]>
PR-URL: #22262 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Trivikram Kamat <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: George Adams <[email protected]>
PR-URL: nodejs/node#22262 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Trivikram Kamat <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: George Adams <[email protected]>
Was reading http2 docs and found this issue. Looks like a heading doesn't need code tags (``).
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passes