-
Notifications
You must be signed in to change notification settings - Fork 30k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
doc: add more info for timer.setInterval #45232
doc: add more info for timer.setInterval #45232
Conversation
5bb43d9
to
de369ac
Compare
@nodejs/timers |
de369ac
to
62db6ff
Compare
@@ -442,6 +442,8 @@ added: v15.9.0 | |||
--> | |||
|
|||
Returns an async iterator that generates values in an interval of `delay` ms. | |||
If `ref` is `true`, you need to call `next()` of async iterator explicitly | |||
or implicitly to keep the event loop alive. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we usually use the word "open" instead of "alive" to describe the event loop, but let's ping @nodejs/documentation for confirmation.
or implicitly to keep the event loop alive. | |
or implicitly to keep the event loop open . |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The document uses active
and Libuv
uses alive
🤔.
@Trott Hi, can this PR be merged ? |
Yes. If I want to try to get consistency across all our docs regarding event loop terminology, I'll do that in a separate PR. There's no reason to hold this one up over that, though. |
Landed in 4fc6ef5 |
PR-URL: nodejs#45232 Refs: nodejs#45224 Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
add more info for
timer.setInterval
.Refs: #45224
make -j4 test
(UNIX), orvcbuild test
(Windows) passes