node/tools/doc
Tobias Nießen 9564f7a123 tools: fix doc tool behavior for version arrays
Even though the doc tool supports version arrays in theory, it fails to
sort them properly causing the tool to crash.

PR-URL: https://github.com/nodejs/node/pull/22766
Reviewed-By: Gus Caplan <me@gus.host>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: James M Snell <jasnell@gmail.com>
2018-09-19 09:59:42 +02:00
..
LICENSE Mention marked, and add license to doc generator 2012-03-05 10:59:14 -08:00
README.md doc: update tools/doc/README.md 2018-04-16 16:20:09 -07:00
addon-verify.js tools: convert addon-verify to remark 2018-08-15 20:23:17 +10:00
allhtml.js tools: validate apidoc links 2018-07-24 20:49:04 +02:00
alljson.js tools: build all.json by combining generated JSON 2018-07-12 09:16:54 +02:00
apilinks.js tools,doc: apilinks should handle root scenarios 2018-09-10 18:23:44 +02:00
common.js tools: fix doc tool behavior for version arrays 2018-09-19 09:59:42 +02:00
generate.js tools: Include links to source code in documentation 2018-09-06 08:53:57 +02:00
html.js tools: fix doc tool behavior for version arrays 2018-09-19 09:59:42 +02:00
json.js tools: produce JSON documentation using unified/remark/rehype 2018-08-07 08:56:18 +02:00
package-lock.json tools: convert addon-verify to remark 2018-08-15 20:23:17 +10:00
package.json tools: convert addon-verify to remark 2018-08-15 20:23:17 +10:00
type-parser.js process: add allowedNodeEnvironmentFlags property 2018-09-06 08:52:21 +02:00

README.md

Here's how the node docs work.

1:1 relationship from lib/<module>.js to doc/api/<module>.md.

Each type of heading has a description block.

# module

<!--introduced_in=v0.10.0-->

> Stability: 2 - Stable

A description and examples.

## module.property
<!-- YAML
added: v0.10.0
-->

* {type}

A description of the property.

## module.someFunction(x, y, [z=100])
<!-- YAML
added: v0.10.0
-->

* `x` {string} The description of the string.
* `y` {boolean} Should I stay or should I go?
* `z` {number} How many zebras to bring. **Default:** `100`.

A description of the function.

## module.someNewFunction(x)
<!-- YAML
added: REPLACEME
-->

* `x` {string} The description of the string.

This feature is not in a release yet.

## Event: 'blerg'
<!-- YAML
added: v0.10.0
-->

* `anArg` {type} A description of the listener argument.

Modules don't usually raise events on themselves. `cluster` is the
only exception.

## Class: SomeClass
<!-- YAML
added: v0.10.0
-->

A description of the class.

### SomeClass.classMethod(anArg)
<!-- YAML
added: v0.10.0
-->

* `anArg` {Object} Just an argument.
  * `field` {string} `anArg` can have this field.
  * `field2` {boolean} Another field. **Default:** `false`.
* Returns: {boolean} `true` if it worked.

A description of the method for humans.

### SomeClass.nextSibling()
<!-- YAML
added: v0.10.0
-->

* Returns: {SomeClass | null} The next `SomeClass` in line.

`SomeClass` must be registered in `tools/doc/type-parser.js`
to be properly parsed in `{type}` fields.

### SomeClass.someProperty
<!-- YAML
added: v0.10.0
-->

* {string}

The indication of what `someProperty` is.

### Event: 'grelb'
<!-- YAML
added: v0.10.0
-->

* `isBlerg` {boolean}

This event is emitted on instances of `SomeClass`, not on the module itself.
  • Classes have (description, Properties, Methods, Events).
  • Events have (list of listener arguments, description).
  • Functions have (list of arguments, returned value if defined, description).
  • Methods have (list of arguments, returned value if defined, description).
  • Modules have (description, Properties, Functions, Classes, Examples).
  • Properties have (type, description).