| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
I don't think this can be removed without some sort of deprecation cycle. |
Sorry, something went wrong.
This is a semver-major change. Remove SecurePair, createSecure pair from API. Remove internal Connection class and SecurePair tests.
|
Sorry, something went wrong.
|
A deprecation cycle would definitely be required first. |
Sorry, something went wrong.
|
@jasnell what exactly is missing? I believe createSecurePair had a deprecation warning in documentation for quite a long time now... |
Sorry, something went wrong.
|
@indutny I think it needs to be deprecated at the code level via internal/util.deprecate() and not just documentation. Also, tls.createSecurePair() isn't even deprecated in the documentation. |
Sorry, something went wrong.
|
@mscdex perhaps there is a bug in docs, but it is deprecated: https://nodejs.org/api/tls.html#tls_class_cryptostream |
Sorry, something went wrong.
|
@indutny There is no connection between CryptoStream and createSecurePair()/SecurePair in the docs. |
Sorry, something went wrong.
|
@mscdex yeah, looks like we will need to deprecate it first then. 😢 @jhamhader sorry, but this PR will have to wait a release cycle |
Sorry, something went wrong.
|
Will submit a deprecation PR and resume effort on SNI callback issue. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Pull Request check-list
Please make sure to review and check all of these items:
this change (including linting)?
test (or a benchmark) included?
existing APIs, or introduces new ones)?
NOTE: these things are not required to open a PR and can be done
afterwards / while the PR is open.
Affected core subsystem(s)
Please provide affected core subsystem(s) (like buffer, cluster, crypto, etc)
Description of change
Please provide a description of the change here.
This is a semver-major change.
Remove SecurePair, createSecure pair from API.
Remove internal Connection class and SecurePair tests.