-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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: wrap buffer.md at 80 characters #19546
Conversation
ping @mcollina given the objections last time this came up. |
I'm still -1 for the time being on this. Happy for this go to a TSC vote if you feel strongly about it, this has been discussed extensively already and not linting this file was the middle ground that was reached. See the long discussion in #18726. Thanks @apapirovski for the ping. |
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.
making my -1 prominent
@mcollina Your opposition is based on the fact that the whitespace changes will complicate backporting? Or are there other concerns too? |
I’m generically -1 on massive linting changes if I get the chance to review them. Regarding this specifically, yes it is a backport problem. |
If I open backport PRs right now for 9.x, 8.x, and 6.x, would that be enough to remove your objection? Or is the churn here still just too much? |
IMHO it is too much churn. |
As I said, I should have brought the matter to the TSC back then. Anyway, feel free to land. |
There's changes in here that break links. Still need to address those. So please don't land. I'll add the |
doc/api/buffer.md
Outdated
* [`Buffer.from(array)`] returns a new `Buffer` containing a *copy* of the | ||
provided octets. | ||
* [`Buffer.from(arrayBuffer[, byteOffset [, length]])`] | ||
[`Buffer.from(arrayBuffer)`] returns a new `Buffer` that *shares* the same |
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.
@Trott I could be wrong, but I think the broken links can be fixed by moving the opening [
up to the previous line.
66c9e5d
to
fa7b2c3
Compare
d425e0d
to
ec7b5a7
Compare
Dismissing to indicate that it is fine to land this PR as mentioned in a former comment.
Ping @Trott |
@BridgeAR Working through this slowly and opening other PRs when I find bigger issues that need addressing near one of these line-wraps. As I rebase, the change set gets smaller and smaller, which I think is A Good Thing. If having this open is a problem, feel free to close it. Otherwise, it's mildly convenient for me and it will land eventually, just not this week. |
94cb561
to
18e5b0c
Compare
a54da8e
to
c6ef2a2
Compare
Wrap `buffer.md` at 80 characters and enforce with linter.
Wrap `buffer.md` at 80 characters and enforce with linter. PR-URL: nodejs#19546 Reviewed-By: Yuta Hiroto <hello@hiroppy.me> Reviewed-By: Daniel Bevenius <daniel.bevenius@gmail.com> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com>
Landed in 743341d |
Wrap `buffer.md` at 80 characters and enforce with linter. PR-URL: #19546 Reviewed-By: Yuta Hiroto <hello@hiroppy.me> Reviewed-By: Daniel Bevenius <daniel.bevenius@gmail.com> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com>
Wrap
buffer.md
at 80 characters and enforce with linter.Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes