Skip to content

Conversation

@antsmartian
Copy link
Contributor

@antsmartianantsmartian commented Aug 11, 2018

Was reading http2 docs and found this issue. Looks like a heading doesn't need code tags (``).

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • documentation is changed or added
  • commit message follows commit guidelines

@nodejs-github-botnodejs-github-bot added doc Issues and PRs related to the documentations. http2 Issues or PRs related to the http2 subsystem. labels Aug 11, 2018
@trivikr
Copy link
Member

@trivikrtrivikr added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Aug 11, 2018
@Trott
Copy link
Member

@vsemozhetbyt@rubys (just to get the eyes of the people most familiar with our current markdown processing quirks and bugs)

@vsemozhetbyt
Copy link
Contributor

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
Copy link
Contributor

vsemozhetbyt commented Aug 11, 2018

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
Copy link
Member

@antsmartian can you please resolve the conflicts?

Copy link
Contributor

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?

Copy link
ContributorAuthor

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.

Copy link
ContributorAuthor

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.

@antsmartian
Copy link
ContributorAuthor

@vsemozhetbyt Now it should be good to go. cc @gdams fixed the conflicts.

@gdams
Copy link
Member

@gdams
Copy link
Member

landed in: fc84666

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author readyPRs that have at least one approval, no pending requests for changes, and a CI started.docIssues and PRs related to the documentations.http2Issues or PRs related to the http2 subsystem.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants

@antsmartian@trivikr@Trott@vsemozhetbyt@gdams@jasnell@nodejs-github-bot