-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
doc: fix some links #14400
doc: fix some links #14400
Conversation
I've fixed another one in |
doc/guides/writing-tests.md
Outdated
(https://github.com/nodejs/lts). [node.green](http://node.green/) lists | ||
available features in each release. | ||
features that can be used directly without a flag in | ||
[all maintained branches](https://github.com/nodejs/lts). |
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.
Maybe move these links to the bottom as we usually do?
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.
There are 5 links in the doc without references. Should I move them all to the bottom?
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 am not entirely sure, but considering that there are three links in the footer, I would prefer consistency. In most cases that makes sense, but barely for [here](https://github.com/nodejs/testing/issues/27)
. I am fine if you leave it as it is, just wanted to suggest that, didn't know there were so many other "inline" links. So feel free to change it or leave it, I really don't know what we should go for.
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.
Done for all except [here]
ad hoc link.
Landed in 4d1e086 |
PR-URL: #14400 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Yuta Hiroto <[email protected]> Reviewed-By: Khaidi Chu <[email protected]> Reviewed-By: James M Snell <[email protected]>
PR-URL: #14400 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Yuta Hiroto <[email protected]> Reviewed-By: Khaidi Chu <[email protected]> Reviewed-By: James M Snell <[email protected]>
PR-URL: nodejs#14400 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Yuta Hiroto <[email protected]> Reviewed-By: Khaidi Chu <[email protected]> Reviewed-By: James M Snell <[email protected]>
Backport-PR-URL: #19447 PR-URL: #14400 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Yuta Hiroto <[email protected]> Reviewed-By: Khaidi Chu <[email protected]> Reviewed-By: James M Snell <[email protected]>
Checklist
Affected core subsystem(s)
doc
I am not sure about
[][]
type links in the DNS doc. Do they mean two-dimensional array, as stated in thedns.resolveTxt()
description? If so, let me know to revert (and they should be fixed in doc tools as now they are not rendered as links).