| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Review requested:
|
Sorry, something went wrong.
|
@noel046 Thank you for contribution. Commit title needs to be started with subsystem like doc: update incorrect links. Please follow Commit message guidelines. |
Sorry, something went wrong.
|
@noel046 For now, PR title is only changed. But we need to change commit title(not PR of github) in git. |
Sorry, something went wrong.
The merge commit will need to be removed too. I'll do that now and force push. |
Sorry, something went wrong.
|
The CI failure is relevant. This breaks links in the single-page version of the doc. |
Sorry, something went wrong.
| [`'drain'`]: #event-drain | ||
| [`'end'`]: #event-end | ||
| [`'error'`]: #event-error_1 | ||
| [`'error'`]: #event-error-1 |
There was a problem hiding this comment.
The current anchor exists in our HTML docs. The new one does not. What is the motivation for this change? Is it to fix something in the GitHub markdown rendering of this doc?
Sorry, something went wrong.
There was a problem hiding this comment.
+1, on our tooling we replace dots with nothing and underscores with hyphens. You can see it here: https://github.com/nodejs/node/blob/main/tools/doc/html.mjs#L426 (We do the same on nodejs.dev here https://github.com/nodejs/nodejs.dev/blob/main/util-node/createSlug.js#L1)
Sorry, something went wrong.
|
Please also add a Fixes: https://github.com/nodejs/node/issues/47070 to the commit message. |
Sorry, something went wrong.
|
Can we get this merged soon? We've been getting more and more identical PRs for the same (or a subset of) changes. |
Sorry, something went wrong.
|
@mscdex did the issues Trott and me mentioned get resolved? |
Sorry, something went wrong.
|
@ovflowd I don't know. However from my recollection we tend to give the first to submit a PR for a specific set of changes priority, but as this PR has been open for over a month with others willing to make the same changes, we need to decide whether to continue waiting or close this PR and give others a chance to make the changes needed. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Fixes: #47070