Open dbauszus-glx opened 4 days ago
I cleaned up the modules and globals which were wrongly defined in their JSDOC block.
I added stumps for the infoj-entry
, layer
, layer-cluster
, and layer-style
typedefs.
Please don't merge this until everyone in the reviewers list has looked at this.
I have moved and updated the README.md for the XYZ api to the api folder.
I added the html extension to the express docs route allowing to link to static pages in the docs folder without the html extension.
I have updated the api module jsdoc and added the req, res typedef.
I have updated the mapp readme with links to mapp and ui modules and core requirements for each.
Modules
JSDoc comments for modules must include the module path as title and any
@requires
linking the page to other pages in the docs directory.A small description should be provided to outline the module's purpose.
Functions
Comments for functions begin with the
@function
tag. Functions should not be anonymous.@async
functions should be commented as such.Each function comment should include an
@description
tag. It is recommended to use a new line for multiline descriptions.The
@param
tag list should include only params used as function arguments.Parameter properties should be included if used in the method. Any optional [property] are marked in square brackets.
A global typedef should be created for common Mapp objects.
The
@return
comment tag should state whether a promise is returned which may return an Error object, eg.@returns {Promise<Object|Error>}
Decorator methods
Decorator methods should always return a typedef.
@deprecated methods.
Functions no longer in use but kept with a warning for legacy configurations should be marked as
@deprecated
.@typedef [GLOBAL]
Mapp type object should be defined as global typedefs.
Typedef properties should be defined as typedef using a dash naming convention. eg. The style object property of a
layer
typedef will be defined aslayer-style
, the theme object of a layer-style typedef will be type defined aslayer-style-theme
.@example
An @example does not require a code block [```JS] definition. At examples should be reserved for codepen examples which can be run. Code blocks should be used for code syntax highlighting in the rendered markdown.