Commit ee593ca
doc: fix dnsPromises.lookup verbatim default
The verbatim default flipped to true in v17 (#39987), but the
dnsPromises.lookup docs still say false. The order bullet right above
it and the dns.lookup section both already say the addresses are not
reordered by default, so this bullet was contradicting them.
Signed-off-by: BIGSUS24 <152616194+BIGSUS24@users.noreply.github.com>
PR-URL: #64658
Reviewed-By: Tim Perry <pimterry@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Ethan Arrowood <ethan@arrowood.dev>1 parent 6e10012 commit ee593ca
1 file changed
Lines changed: 1 addition & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -1113,8 +1113,7 @@ changes: | |||
| 1113 | 1113 | IPv4 addresses are placed before IPv6 addresses. | |
| 1114 | 1114 | This option will be deprecated in favor of `order`. When both are specified, | |
| 1115 | 1115 | `order` has higher precedence. New code should only use `order`. | |
| 1116 | - **Default:** currently `false` (addresses are reordered) but this is | ||
| 1117 | - expected to change in the not too distant future. Default value is | ||
| 1116 | + **Default:** `true` (addresses are not reordered). Default value is | ||
| 1118 | 1117 | configurable using [`dns.setDefaultResultOrder()`][] or | |
| 1119 | 1118 | [`--dns-result-order`][]. | |
| 1120 | 1119 | ||
0 commit comments