crypto: make _toBuf non-enumerable#22551
Closed
tniessen wants to merge 1 commit intonodejs:masterfrom
Closed
Conversation
cjihrig
approved these changes
Aug 27, 2018
thefourtheye
approved these changes
Aug 27, 2018
Member
Author
jasnell
approved these changes
Aug 27, 2018
trivikr
approved these changes
Aug 27, 2018
addaleax
approved these changes
Aug 27, 2018
Member
addaleax
left a comment
There was a problem hiding this comment.
I guess this depends on a semver-major change, so it doesn’t really matter, but I don’t think we need to consider this one.
Member
Author
|
@addaleax I thought we considered such changes as semver-major themselves, I am not sure though. |
Member
Author
|
Landed in 503fd55. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
After landing #22501, I noticed that I did not make
_toBufnon-enumerable. Following the discussion in #22519, I believe it should be, so here is that. Partially also for consistency with the rest ofcrypto.js.cc @nodejs/crypto
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passes