-
Notifications
You must be signed in to change notification settings - Fork 30.3k
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
streams: refactor LazyTransform to internal/ #2566
streams: refactor LazyTransform to internal/ #2566
Conversation
This commit refactors LazyTransform from the crypto implementation (lib/crypto.js) into an internal module (not publicy accessible) in internal/streams/LazyTransform.js. This promotes a more modular core design and removes code bloat in crypto, as LazyTransform didn't specifically have anything to do with cryptography, but rather a fast way to support two APIs on a stream.
r=@nodejs/crypto ? |
I think it would be the first module to use camel case file name. Should it really have it? Otherwise, LGTM |
I don't have a preference, I can change it to |
I think |
Updated with a rename. Here is a CI: https://ci.nodejs.org/view/iojs/job/node-test-pull-request/284/. |
LGTM |
Hmm, not sure if CI is happy. New run: https://ci.nodejs.org/job/node-test-pull-request/297/ |
@brendanashworth CI seems good. |
This commit refactors LazyTransform from the crypto implementation (lib/crypto.js) into an internal module (not publicy accessible) in internal/streams/lazy_transform.js. This promotes a more modular core design and removes code bloat in crypto, as LazyTransform didn't specifically have anything to do with cryptography, but rather a fast way to support two APIs on a stream. PR-URL: #2566 Reviewed-By: Fedor Indutny <fedor.indutny@gmail.com>
Thank you, landed in c70c778. |
This commit refactors LazyTransform from the crypto implementation (lib/crypto.js) into an internal module (not publicy accessible) in internal/streams/lazy_transform.js. This promotes a more modular core design and removes code bloat in crypto, as LazyTransform didn't specifically have anything to do with cryptography, but rather a fast way to support two APIs on a stream. PR-URL: #2566 Reviewed-By: Fedor Indutny <fedor.indutny@gmail.com>
This commit refactors LazyTransform from the crypto implementation (lib/crypto.js) into an internal module (not publicy accessible) in internal/streams/lazy_transform.js. This promotes a more modular core design and removes code bloat in crypto, as LazyTransform didn't specifically have anything to do with cryptography, but rather a fast way to support two APIs on a stream. PR-URL: #2566 Reviewed-By: Fedor Indutny <fedor.indutny@gmail.com>
This commit refactors
LazyTransform
from the crypto implementation(
lib/crypto.js
) into an internal module (not publicy accessible) ininternal/streams/LazyTransform.js
. This promotes a more modular coredesign and removes code bloat in crypto, as
LazyTransform
didn'tspecifically have anything to do with cryptography, but rather a fast
way to support two APIs on a stream.