tls: use correct class name in deprecation message

`tls.Socket` does not exist, and the deprecation message should refer to `tls.TLSSocket` (like the documentation for the deprecation message already does). PR-URL: #17561 Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Jon Moss <[email protected]> Reviewed-By: Timothy Gu <[email protected]> Reviewed-By: Anatoli Papirovski <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]>
nodejs · Dec 12, 2017 · d11f7d5 · d11f7d5
1 parent 727339e
commit d11f7d5
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/lib/_tls_legacy.js b/lib/_tls_legacy.js
@@ -949,6 +949,6 @@ module.exports = {
   createSecurePair:
     internalUtil.deprecate(createSecurePair,
                            'tls.createSecurePair() is deprecated. Please use ' +
-                           'tls.Socket instead.', 'DEP0064'),
+                           'tls.TLSSocket instead.', 'DEP0064'),
   pipe
 };
diff --git a/test/parallel/test-tls-legacy-deprecated.js b/test/parallel/test-tls-legacy-deprecated.js
@@ -9,7 +9,7 @@ const tls = require('tls');
 
 common.expectWarning(
   'DeprecationWarning',
-  'tls.createSecurePair() is deprecated. Please use tls.Socket instead.'
+  'tls.createSecurePair() is deprecated. Please use tls.TLSSocket instead.'
 );
 
 assert.doesNotThrow(() => tls.createSecurePair());