-
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: add note to util.isBuffer #3790
Conversation
LGTM |
Of note though, it's just an |
Since it's deprecated why still keep the usage description of the old API? Shall we reduce to only the note of "Use |
LGTM. The message might be better with the description of the function, above the code example. |
If it is deprecated can we use the stability note like in other functions in it? |
LGTM |
@cjihrig are you saying move the note to the top of the section? |
@pmq20 well, it hasn't been removed yet. I think we should keep that part until we actually remove the api |
@evanlucas I meant move it from line 418 to line 407. If you think it would be more likely to be noticed. |
yea, looking back at it, I think that makes more sense |
6ddf6bb
to
8705d4e
Compare
Updated. PTAL |
LGTM |
Since util.isBuffer is deprecated, we should be explicit that Buffer.isBuffer should be used instead. PR-URL: nodejs#3790 Reviewed-By: Jeremiah Senkpiel <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]>
8705d4e
to
7cb3a54
Compare
Landed in 7cb3a54. Thanks! |
Ah... The deprecation notice is already there. Sorry about the fuss |
Since util.isBuffer is deprecated, we should be explicit that Buffer.isBuffer should be used instead. PR-URL: #3790 Reviewed-By: Jeremiah Senkpiel <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]>
Since util.isBuffer is deprecated, we should be explicit that Buffer.isBuffer should be used instead. PR-URL: #3790 Reviewed-By: Jeremiah Senkpiel <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]>
landed in v4.x-staging in 3435f87 |
Since util.isBuffer is deprecated, we should be explicit that Buffer.isBuffer should be used instead. PR-URL: #3790 Reviewed-By: Jeremiah Senkpiel <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]>
Since util.isBuffer is deprecated, we should be explicit that Buffer.isBuffer should be used instead. PR-URL: #3790 Reviewed-By: Jeremiah Senkpiel <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]>
Since util.isBuffer is deprecated, we should be explicit that Buffer.isBuffer should be used instead. PR-URL: #3790 Reviewed-By: Jeremiah Senkpiel <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]>
Since
util.isBuffer
is deprecated, we should be explicit thatBuffer.isBuffer
should be used instead.