7640bcd163
Currently the search term is matched against the longname of members. Because of this most members are matched when searching for a class / module and also searching for 'mod' matches everything as all longnames start with 'module:'
API Documentation
This directory contains configuration (conf.json), static content (index.md), template (template/) and plugins (plugins/) for the JSDoc3 API generator.
Documenting the source code
JSDoc annotations are used for metadata used by the compiler, for defining the user facing API, and for user documentation.
In the simplest case, a JSDoc block can look like this:
/**
* Add the given control to the map.
* @param {ol.control.Control} control Control.
* @api
*/
ol.Map.prototype.addControl = function(control) {
// ...
};
The first line is text for the user documentation. This can be long, and it can contain Markdown.
The second line tells the Closure compiler the type of the argument.
The third line (@api) marks the method as part of the api and thus exportable. Without such an api annotation, the method will not be documented in the generated API documentation. Symbols without an api annotation will also not be exportable.
The @api annotation can be used in conjunction with the @inheritDoc annotation to export a symbol that is documented on a parent class (where the method may be abstract). In general, @api annotations should never be used on abstract methods (only on their implementations).
Events
Events are documented using @fires and @event annotations:
/**
* Constants for event names.
* @enum {string}
*/
ol.MapBrowserEventType = {
/**
* A true single click with no dragging and no double click. Note that this
* event is delayed by 250 ms to ensure that it is not a double click.
* @event ol.MapBrowserEvent#singleclick
* @api
*/
SINGLECLICK: 'singleclick',
// ...
};
Note the value of the @event annotation. The text before the hash refers to the event class that the event belongs to, and the text after the hash is the type of the event.
To document which events are fired by a class or method, the @fires annotation is used:
/**
* @fires ol.MapBrowserEvent
* @fires ol.MapEvent
* @fires ol.render.Event
* ...
*/
ol.Map = function(options) {
// ...
};
Observable Properties
Observable properties are documented using the @observable annotation. This annotation is added to the getter of an observable property. If an observable property is also settable, the setter is annotated with @observable as well.