-
Notifications
You must be signed in to change notification settings - Fork 30k
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
crypto: make _toBuf non-enumerable #22551
Closed
Closed
Conversation
This file contains 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
tniessen
added
the
semver-major
PRs that contain breaking changes and should be released in the next major version.
label
Aug 27, 2018
nodejs-github-bot
added
the
crypto
Issues and PRs related to the crypto subsystem.
label
Aug 27, 2018
cjihrig
approved these changes
Aug 27, 2018
thefourtheye
approved these changes
Aug 27, 2018
tniessen
added
the
author ready
PRs that have at least one approval, no pending requests for changes, and a CI started.
label
Aug 27, 2018
jasnell
approved these changes
Aug 27, 2018
trivikr
approved these changes
Aug 27, 2018
addaleax
approved these changes
Aug 27, 2018
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 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.
@addaleax I thought we considered such changes as semver-major themselves, I am not sure though. |
Landed in 503fd55. |
tniessen
removed
the
author ready
PRs that have at least one approval, no pending requests for changes, and a CI started.
label
Sep 12, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
crypto
Issues and PRs related to the crypto subsystem.
semver-major
PRs that contain breaking changes and should be released in the next major version.
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
_toBuf
non-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