| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
Can you order this alphabetically like the rest? |
Sorry, something went wrong.
|
Also, it'd be good to expand the parameter bits to be in-line with this other buffers PR: #4873 |
Sorry, something went wrong.
There was a problem hiding this comment.
UTF**-**8
Sorry, something went wrong.
There was a problem hiding this comment.
Also you should need to mention the default encoding at all since it is listed above.
Sorry, something went wrong.
There was a problem hiding this comment.
It's rendered "UTF8" everywhere else in this file. I think this is fine.
Sorry, something went wrong.
There was a problem hiding this comment.
Can you wrap each type separately, please?
Sorry, something went wrong.
There was a problem hiding this comment.
It's done like this everywhere else in the file -- eg indexOf, includes, and fill
I can change all of those places if you want--LMK
Sorry, something went wrong.
There was a problem hiding this comment.
@Qard added a commit that wraps types separately everywhere there's a list
Sorry, something went wrong.
There was a problem hiding this comment.
Unfortunately wrapping the three separately confuses the JSON documentation generation IIRC.
Sorry, something went wrong.
|
LGTM |
Sorry, something went wrong.
There was a problem hiding this comment.
Could you please add
const Buffer = require('buffer').Buffer;
Sorry, something went wrong.
There was a problem hiding this comment.
Is it needed for the linter ? Buffer is global.
Sorry, something went wrong.
There was a problem hiding this comment.
The linter does complain about it
Sorry, something went wrong.
There was a problem hiding this comment.
@tflanagan no other code sample in this doc does that
which linter are you talking about? make test and make doc both run without errors
Sorry, something went wrong.
|
@jasnell thanks for the review. i just rebased because there were conflicts. the PR is even smaller now -- it only adds the Buffer.lastIndexOf section to the docs and doesn't modify any existing sections |
Sorry, something went wrong.
|
LGTM |
Sorry, something went wrong.
Sorry, something went wrong.
|
That's what I figured... any reason not to simply bundle the two commits into the single PR #4846? Would make it easier to land. |
Sorry, something went wrong.
|
Agreed, it's better that docs commits of new features are included in the PR of the feature itself and just mention @nodejs/documentation in the issue to summon us docs folks for review. |
Sorry, something went wrong.
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Complements #4604
Together they fix #4846