| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
1 parent d7b95f1 commit f90cf19
14 files changed
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -51,10 +51,6 @@ | |||
| 51 | 51 | * References to constructor instances should use camelCase. | |
| 52 | 52 | * References to methods should be used with parentheses: for example, | |
| 53 | 53 | `socket.end()` instead of `socket.end`. | |
| 54 | - * To draw special attention to a note, adhere to the following guidelines: | ||
| 55 | - * Make the "Note:" label italic, i.e. `*Note*:`. | ||
| 56 | - * Use a capital letter after the "Note:" label. | ||
| 57 | - * Preferably, make the note a new paragraph for better visual distinction. | ||
| 58 | 54 | * Function arguments or object properties should use the following format: | |
| 59 | 55 | * ``` * `name` {type|type2} Optional description. **Default:** `value`. ``` | |
| 60 | 56 | <!--lint disable maximum-line-length remark-lint--> | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -426,10 +426,10 @@ the function does not return a promise, `assert.doesNotReject()` will return a | |||
| 426 | 426 | rejected `Promise` with an [`ERR_INVALID_RETURN_VALUE`][] error. In both cases | |
| 427 | 427 | the error handler is skipped. | |
| 428 | 428 | ||
| 429 | - Please note: Using `assert.doesNotReject()` is actually not useful because there | ||
| 430 | - is little benefit by catching a rejection and then rejecting it again. Instead, | ||
| 431 | - consider adding a comment next to the specific code path that should not reject | ||
| 432 | - and keep error messages as expressive as possible. | ||
| 429 | + Using `assert.doesNotReject()` is actually not useful because there is little | ||
| 430 | + benefit in catching a rejection and then rejecting it again. Instead, consider | ||
| 431 | + adding a comment next to the specific code path that should not reject and keep | ||
| 432 | + error messages as expressive as possible. | ||
| 433 | 433 | ||
| 434 | 434 | If specified, `error` can be a [`Class`][], [`RegExp`][] or a validation | |
| 435 | 435 | function. See [`assert.throws()`][] for more details. | |
@@ -472,8 +472,8 @@ changes: | |||
| 472 | 472 | ||
| 473 | 473 | Asserts that the function `fn` does not throw an error. | |
| 474 | 474 | ||
| 475 | - Please note: Using `assert.doesNotThrow()` is actually not useful because there | ||
| 476 | - is no benefit by catching an error and then rethrowing it. Instead, consider | ||
| 475 | + Using `assert.doesNotThrow()` is actually not useful because there | ||
| 476 | + is no benefit in catching an error and then rethrowing it. Instead, consider | ||
| 477 | 477 | adding a comment next to the specific code path that should not throw and keep | |
| 478 | 478 | error messages as expressive as possible. | |
| 479 | 479 | ||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -1056,9 +1056,9 @@ child process may not actually terminate the process. | |||
| 1056 | 1056 | ||
| 1057 | 1057 | See kill(2) for reference. | |
| 1058 | 1058 | ||
| 1059 | - Also note: on Linux, child processes of child processes will not be terminated | ||
| 1059 | + On Linux, child processes of child processes will not be terminated | ||
| 1060 | 1060 | when attempting to kill their parent. This is likely to happen when running a | |
| 1061 | - new process in a shell or with use of the `shell` option of `ChildProcess`: | ||
| 1061 | + new process in a shell or with the use of the `shell` option of `ChildProcess`: | ||
| 1062 | 1062 | ||
| 1063 | 1063 | ```js | |
| 1064 | 1064 | 'use strict'; | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -845,7 +845,7 @@ const crypto = require('crypto'); | |||
| 845 | 845 | const alice = crypto.createECDH('secp256k1'); | |
| 846 | 846 | const bob = crypto.createECDH('secp256k1'); | |
| 847 | 847 | ||
| 848 | - // Note: This is a shortcut way to specify one of Alice's previous private | ||
| 848 | + // This is a shortcut way of specifying one of Alice's previous private | ||
| 849 | 849 | // keys. It would be unwise to use such a predictable private key in a real | |
| 850 | 850 | // application. | |
| 851 | 851 | alice.setPrivateKey( | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -419,7 +419,7 @@ added: v8.6.0 | |||
| 419 | 419 | ||
| 420 | 420 | * `multicastInterface` {string} | |
| 421 | 421 | ||
| 422 | - *Note: All references to scope in this section are referring to | ||
| 422 | + *All references to scope in this section are referring to | ||
| 423 | 423 | [IPv6 Zone Indices][], which are defined by [RFC 4007][]. In string form, an IP | |
| 424 | 424 | with a scope index is written as `'IP%scope'` where scope is an interface name | |
| 425 | 425 | or interface number.* | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -122,7 +122,7 @@ if (cluster.isMaster) { | |||
| 122 | 122 | d.on('error', (er) => { | |
| 123 | 123 | console.error(`error ${er.stack}`); | |
| 124 | 124 | ||
| 125 | - // Note: We're in dangerous territory! | ||
| 125 | + // We're in dangerous territory! | ||
| 126 | 126 | // By definition, something unexpected occurred, | |
| 127 | 127 | // which we probably didn't want. | |
| 128 | 128 | // Anything can happen now! Be very careful! | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -54,7 +54,7 @@ path.posix.basename('/tmp/myfile.html'); | |||
| 54 | 54 | // Returns: 'myfile.html' | |
| 55 | 55 | ``` | |
| 56 | 56 | ||
| 57 | - *Note:* On Windows Node.js follows the concept of per-drive working directory. | ||
| 57 | + On Windows Node.js follows the concept of per-drive working directory. | ||
| 58 | 58 | This behavior can be observed when using a drive path without a backslash. For | |
| 59 | 59 | example, `path.resolve('c:\\')` can potentially return a different result than | |
| 60 | 60 | `path.resolve('c:')`. For more information, see | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -7,7 +7,7 @@ | |||
| 7 | 7 | <!--name=vm--> | |
| 8 | 8 | ||
| 9 | 9 | The `vm` module provides APIs for compiling and running code within V8 Virtual | |
| 10 | - Machine contexts. **Note that the `vm` module is not a security mechanism. Do | ||
| 10 | + Machine contexts. **The `vm` module is not a security mechanism. Do | ||
| 11 | 11 | not use it to run untrusted code**. The term "sandbox" is used throughout these | |
| 12 | 12 | docs simply to refer to a separate context, and does not confer any security | |
| 13 | 13 | guarantees. | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -6,7 +6,7 @@ Each release line has a staging branch that the releaser will use as a scratch | |||
| 6 | 6 | pad while preparing a release. The branch name is formatted as follows: | |
| 7 | 7 | `vN.x-staging` where `N` is the major release number. | |
| 8 | 8 | ||
| 9 | - *Note*: For the active staging branches see the [Release Schedule][]. | ||
| 9 | + For the active staging branches see the [Release Schedule][]. | ||
| 10 | 10 | ||
| 11 | 11 | ## What needs to be backported? | |
| 12 | 12 | ||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -228,7 +228,7 @@ to be cherry-picked in the Node.js repository and V8-CI must test the change. | |||
| 228 | 228 | * Open a cherry-pick PR on `nodejs/node` targeting the *vY.x-staging* branch | |
| 229 | 229 | and notify the `@nodejs/v8` team. | |
| 230 | 230 | * Run the Node.js [V8 CI] in addition to the [Node.js CI]. | |
| 231 | - Note: The CI uses the `test-v8` target in the `Makefile`, which uses | ||
| 231 | + The CI uses the `test-v8` target in the `Makefile`, which uses | ||
| 232 | 232 | `tools/make-v8.sh` to reconstruct a git tree in the `deps/v8` directory to | |
| 233 | 233 | run V8 tests. | |
| 234 | 234 | ||
| Back | FazBrowse Home | New Git URL |
0 commit comments