Skip to content

Commit 2c4ef25

Browse files
authored
doc: rename warn-with-error to warn-with-error-code (#872)
1 parent fb9f754 commit 2c4ef25

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

surveys/promise-rejections/survey.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -244,7 +244,7 @@ Consider the following modes:
244244
- `strict`: raise an uncaught exception similar to `throw new Error()` that is not caught. `unhandledRejection` listeners do not prevent raising the exception
245245
- `throw`: raise an uncaught exception similar to `throw new Error()` that is not caught. `unhandledRejection` listeners take precedence and prevent raising the exception
246246
- `warn`: outputs a warning as soon as possible. Continues running after the warning is emitted. If the process exits and no status code was set, the process exits with a success code. This is similar to what browser consoles do
247-
- `warn-with-error`: outputs a warning as soon as possible. Continues running after the warning is emitted. If the process exits and no status code was set, the process exits with an error code
247+
- `warn-with-error-code`: outputs a warning as soon as possible. Continues running after the warning is emitted. If the process exits and no status code was set, the process exits with an error code
248248
- `none`: do nothing
249249

250250
For all the modes, the action (raise an exception output a warning) will happen on `nextTick`.
@@ -254,6 +254,6 @@ Which one you think should be the default on Node.js?
254254
- [ ] `strict`
255255
- [ ] `throw`
256256
- [ ] `warn`
257-
- [ ] `warn-with-error`
257+
- [ ] `warn-with-error-code`
258258
- [ ] `none`
259259
- [ ] Other (please elaborate)

0 commit comments

Comments
 (0)