lukechilds/node - node - Gitea: Git with a cup of tea

Commit Graph

Author	SHA1	Message	Date
Omer Wazir	ba40942ad2	doc: fix sentence grammar timers.markdown Just added ', it' because the phrasing did not seem correct. PR-URL: https://github.com/iojs/io.js/pull/815 Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>	10 years ago
Ben Noordhuis	789bbb91d3	doc: update node.js references in api docs Fixes: https://github.com/iojs/io.js/issues/740 PR-URL: https://github.com/iojs/io.js/pull/750 Reviewed-By: Colin Ihrig <cjihrig@gmail.com>	10 years ago
Brendan Ashworth	9bca8a0a91	doc: fixes grammar in timers/tls This commit fixes a few grammar issues located within the doc files for timers and tls. They primarily include incorrect use of a / an and a single insertion of a comma. same as [this PR](https://github.com/joyent/node/pull/8581) Reviewed-By: Fedor Indutny <fedor@indutny.com> PR-URL: https://github.com/iojs/io.js/pull/76	10 years ago
Brendan Ashworth	70195acbe3	doc: fix grammar and wording in tls and timers In `tls.markdown`, there was a misuse of 'a' which has been replaced with 'an'. In `timers.markdown`... line 31: misuse of 'a', replaced with 'an' line 59: unclear wording, haywire 'a', added new comma	10 years ago
Trevor Norris	f2a78de6ec	doc: fix optional parameter parsing The parameter parser specifically looked for the old bracket syntax. This generated a lot of warnings when building the docs. Those warnings have been fixed by changing the parsing logic. Signed-off-by: Trevor Norris <trev.norris@gmail.com>	10 years ago
Trevor Norris	51b6b6844e	doc: fix brackets for optional parameters Documentation incorrectly used bracket notation for optional parameters. This caused inconsistencies in usage because of examples like the following: fs.write(fd, data[, position[, encoding]], callback) This simply fixes all uses of bracket notation in documentation. Signed-off-by: Trevor Norris <trev.norris@gmail.com> Reviewed-by: Fedor Indutny <fedor@indutny.com>	10 years ago
Christian	b222374b07	doc: changed timer id to object fix #7074	11 years ago
Timothy J Fontaine	f88b8dad84	test: regression test for #5798 setImmediate	12 years ago
Trevor Norris	71ade1c212	doc: remove mention of maxTickDepth maxTickDepth has been removed, but mention of it was left in the docs. Also added explanation that nextTick is allowed to starve I/O.	12 years ago
Shigeki Ohtsu	401cef797d	doc: add setImmediate execute timing description	12 years ago
Timothy J Fontaine	382f22f229	timers: implement setImmediate	13 years ago
Timothy J Fontaine	bdd1a740cb	add docs for socket/server/timer unref and ref	13 years ago
isaacs	2d44dcc8be	doc: Add stability indicators to documentation	13 years ago
isaacs	4ed05da2be	doc refactor: timers	13 years ago
isaacs	c4d6c7f829	doc refactor: timers	13 years ago
Ryan Dahl	69c35f990f	Doc fixes Fixes #1701. Thanks baudehlo.	13 years ago
Thomas Shinnick	4cf0ce5bb4	docs: typos and minor edits in several modules Mostly quite minor edits. Those possibly of more interest are: emitter.setMaxListeners(n) That the limit is per event name for an emitter. fs.readlink() Not a path, but rather the symbolic link's string value, which would be at best a partial path, certainly not a 'resolvedPath' global.__filename This may be "well-known" but this is a full path to the module that referencing code is running in. It is not the main program's path, unless you are in the main program. Each module knows only its own path. server.listen(port,...) I actually needed this functionality... "gimme just _any_ next port" stream.end() stream.destroy() Yeah, everybody knows what happens to the queued data, but let's make it really explicit for the first readers.	14 years ago
Micheil Smith	e190c9616e	Splitting documentation	14 years ago

17 Commits (14174a95a597cac7b848fe4b3e439814390d6ec6)