Skip to content
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: consolidate timers docs in timers.markdown #5837

Closed
wants to merge 1 commit into from

Conversation

bengl
Copy link
Member

@bengl bengl commented Mar 21, 2016

Pull Request check-list

  • Does make -j8 test (UNIX) or vcbuild test nosign (Windows) pass with
    this change (including linting)?
  • Is the commit message formatted according to [CONTRIBUTING.md][0]?
  • If this change fixes a bug (or a performance problem), is a regression
    test (or a benchmark) included?
  • Is a documentation update included (if this change modifies
    existing APIs, or introduces new ones)?

Affected core subsystem(s)

doc

Description of change

  • Rather than attempting to keep two versions of docs for timers up to
    date, keep them in timers.markdown, and leave references to them in
    globals.markdown.
  • Add setImmediate and clearImmediate to globals.markdown.
  • Change "To schedule" to "Schedules" in timers.markdown.

This implements my comment in #5830.

@jasnell
Copy link
Member

jasnell commented Mar 21, 2016

@nodejs/documentation @Fishrock123

@jasnell jasnell added doc Issues and PRs related to the documentations. timers Issues and PRs related to the timers subsystem / setImmediate, setInterval, setTimeout. lts-watch-v4.x labels Mar 21, 2016
@benjamingr
Copy link
Member

+1 and LGTM.

@eljefedelrodeodeljefe
Copy link
Contributor

LGTM, very reasonable.

@Fishrock123
Copy link
Contributor

Lgtm

@bengl
Copy link
Member Author

bengl commented Mar 22, 2016

Also: happy to close this if #5830 winds up making the same change.

@@ -42,7 +42,7 @@ If `callback` is not a function `setImmediate()` will throw immediately.

## setInterval(callback, delay[, arg][, ...])

To schedule the repeated execution of `callback` every `delay` milliseconds.
Schedules the repeated execution of `callback` every `delay` milliseconds.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should the be there in this sentence?

Rather than attempting to keep two versions of docs for timers up to
date, keep them in timers.markdown, and leave references to them in
globals.markdown.

Add setImmediate and clearImmediate to globals.markdown.

Change "To schedule" to "Schedules" in timers.markdown.
@bengl bengl force-pushed the consolidatetimersdocs branch from 312c050 to b31bd49 Compare March 30, 2016 22:53
@bengl
Copy link
Member Author

bengl commented Mar 30, 2016

@thefourtheye I made the changes you suggested.

@claudiorodriguez
Copy link
Contributor

LGTM, I'll be merging this and closing #5830 in 24hs if no one objects.

@thefourtheye
Copy link
Contributor

Probably we should come to an agreement about the way we represent function names as links in the docs. In few places there is [function] and in few other places [function()]. But that can happen in a separate issue.

As far as this patch is concerned, LGTM.

claudiorodriguez pushed a commit that referenced this pull request Apr 2, 2016
Rather than attempting to keep two versions of docs for timers up to
date, keep them in timers.markdown, and leave references to them in
globals.markdown.

Add setImmediate and clearImmediate to globals.markdown.

Change "To schedule" to "Schedules" in timers.markdown.

PR-URL: #5837
Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
Reviewed-By: Claudio Rodriguez <cjrodr@yahoo.com>
Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com>
@claudiorodriguez
Copy link
Contributor

Landed in 33003a5
Should we create that issue in the nodejs/docs repo?

MylesBorins pushed a commit that referenced this pull request Apr 5, 2016
Rather than attempting to keep two versions of docs for timers up to
date, keep them in timers.markdown, and leave references to them in
globals.markdown.

Add setImmediate and clearImmediate to globals.markdown.

Change "To schedule" to "Schedules" in timers.markdown.

PR-URL: #5837
Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
Reviewed-By: Claudio Rodriguez <cjrodr@yahoo.com>
Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com>
This was referenced Apr 5, 2016
MylesBorins pushed a commit that referenced this pull request Apr 8, 2016
Rather than attempting to keep two versions of docs for timers up to
date, keep them in timers.markdown, and leave references to them in
globals.markdown.

Add setImmediate and clearImmediate to globals.markdown.

Change "To schedule" to "Schedules" in timers.markdown.

PR-URL: #5837
Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
Reviewed-By: Claudio Rodriguez <cjrodr@yahoo.com>
Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com>
@MylesBorins MylesBorins mentioned this pull request Apr 11, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc Issues and PRs related to the documentations. timers Issues and PRs related to the timers subsystem / setImmediate, setInterval, setTimeout.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants