DocBlockr

DocBlockr is a package for Sublime Text 2 & 3 which makes writing documentation a breeze. DocBlockr supports JavaScript (including ES6), PHP, ActionScript, Haxe, CoffeeScript, TypeScript, Java, Apex, Groovy, Objective C, C, C++ and Rust.

Installation

Package Control

1. Open Package Control: Preferences -> Package Control
2. Select Package Control: Install Package
3. Type DocBlockr into the search box and select the package to install it

Feature requests & bug reports

You can leave either of these things here. Pull requests are welcomed heartily, but please read CONTRIBUTING.md first! Basically: in this repo, the main development branch is develop and the stable 'production' branch is master. Please remember to base your branch from develop and issue the pull request back to that branch.

Show your love

Changelog

• v2.14.1, 17 Aug 2015
  • Fix deindentation bug with reparsing doc blocks
• v2.14.0, 15 Jun 2015
  • Adds jsdocs_function_description option (thanks to Gerard Roche)
  • Better handling of parser errors (thanks to Gerard Roche)
• v2.13.3, 4 Jun 2015
  • PHP array shorthand is identified correctly (thanks to Gerard Roche)
  • Decorating comments when using tabs for indentation works better (thanks to Jack Cherng)
• v2.13.2, 30 Mar 2015
  • Updated PHPDoc autocompletions to align with the new spec (thanks to Gerard Roche)
  • Properly handle the case when commas appear inside a type name in Java
  • Added link to README in the preferences menu
• v2.13.1, 29 Mar 2015
  • Adds support for Apex language (thanks @michacom)
  • Fixes identifying multidimensional arrays in C/C++
  • Fixes reformatting and reparsing docblocks in Java
  • Adds options to disable:
    • opening an inline docblock with space (jsdocs_quick_open_inline)
    • inline comment decoration (jsdocs_decorate)

Older history can be found in the history file.

Usage

Below are some examples of what the package does. Note that there are no keyboard shortcuts required to trigger these completions - just type as normal and it happens for you!

Docblock completion

Pressing enter or tab after /** (or ###* for Coffee-Script) yields a new line and closes the comment.

Single-asterisk comment blocks behave similarly:

Function documentation

However, if the line directly afterwards contains a function definition, then its name and parameters are parsed and some documentation is automatically added.

Press Tab to move forward through the fields, press Shift+Tab to move back through the fields.

If there are many arguments, or long variable names, it is sometimes useful to spread the arguments across multiple lines. DocBlockr handles this situation too:

In languages which support type hinting or default values, then those types are prefilled as the datatypes.

DocBlockr will try to make an intelligent guess about the return value of the function.

• If the function name is or begins with "set" or "add", then no @return is inserted.
• If the function name is or begins with "is" or "has", then it is assumed to return a Boolean.
• In Javascript, if the function begins with an uppercase letter then it is assumed that the function is a class definition. No @return tag is added.
• In PHP, some of the magic methods have their values prefilled:
  • __construct, __destruct, __set, __unset, __wakeup have no @return tag.
  • __sleep returns an array.
  • __toString returns a string.
  • __isset returns a bool.
• In ES6 Javascript, generator functions get a @yield tag instead of @return

Variable documentation

If the line following the docblock contains a variable declaration, DocBlockr will try to determine the data type of the variable and insert that into the comment.

Press space or shift+enter after an opening /** to insert an inline docblock.

DocBlockr will also try to determine the type of the variable from its name. Variables starting with is or has are assumed to be booleans, and callback, cb, done, fn, and next are assumed to be functions. If you use your own variable naming system, (e.g. hungarian notation: booleans all start with b, arrays start with arr), you can define these rules yourself. Use the jsdocs_notation_map setting, example:

{
    "jsdocs_notation_map": [
        {
            "prefix": "b", /* a prefix, matches only if followed by an underscore or A-Z */
            "type": "bool" /* translates to "Boolean" in javascript, "bool" in PHP */
        },
        {
            "regex": "tbl_?[Rr]ow", /* any arbitrary regex to test against the variable name */
            "type": "TableRow"      /* you can add your own types */
        }
    ]
}

The notation map can also be used to add arbitrary tags, according to your own code conventions. For example, if your conventions state that functions beginning with an underscore are private, you could add this to the jsdocs_notation_map:

{
    "prefix": "_",
    "tags": ["@private"]
}

Comment extension

Pressing enter inside a docblock will automatically insert a leading asterisk and maintain your indentation.

This applies to docblock comments /** like this */ as well as inline double-slash comments // like this

In either case, you can press shift+enter to stop the automatic extension.

Oftentimes, when documenting a parameter, or adding a description to a tag, your description will cover multiple lines. If the line you are on is directly following a tag line, pressing Tab will move the indentation to the correct position.

Comment decoration

If you write a double-slash comment and then press Ctrl+Enter, DocBlockr will 'decorate' that line for you.

// Foo bar baz<<Ctrl+Enter>>

-- becomes

/////////////////
// Foo bar baz //
/////////////////

This can be disabled by changing the jsdocs_decorate setting to false.

Reparsing a DocBlock

Sometimes, you'll perform some action which clears the fields (sections of text which you can navigate through using Tab). This leaves you with a number of placeholders in the DocBlock with no easy way to jump to them.

With DocBlockr, you can reparse a comment and reactivate the fields by pressing the hotkey Alt+Shift+Tab in OS X or Linux, or Alt+W in Windows

Reformatting paragraphs

Inside a comment block, hit Alt+Q to wrap the lines to make them fit within your rulers. If you would like subsequent lines in a paragraph to be indented, you can adjust the jsdocs_indentation_spaces_same_para setting. For example, a value of 3 might look like this:

/**
 * Duis sed arcu non tellus eleifend ullamcorper quis non erat. Curabitur
 *   metus elit, ultrices et tristique a, blandit at justo.
 * @param  {String} foo Lorem ipsum dolor sit amet.
 * @param  {Number} bar Nullam fringilla feugiat pretium. Quisque
 *   consectetur, risus eu pellentesque tincidunt, nulla ipsum imperdiet
 *   massa, sit amet adipiscing dolor.
 * @return {[type]}
 */

Adding extra tags

Finally, typing @ inside a docblock will show a completion list for all tags supported by JSDoc, the Google Closure Compiler, YUIDoc or PHPDoc. Extra help is provided for each of these tags by prefilling the arguments each expects. Pressing Tab will move the cursor to the next argument.

Configuration

You can access the configuration settings by selecting Preferences -> Package Settings -> DocBlockr.

The jsdocs_* prefix is a legacy from days gone by...

• jsdocs_indentation_spaces (Number) The number of spaces to indent after the leading asterisk.

    // jsdocs_indentation_spaces = 1
    /**
     * foo
     */
  
    // jsdocs_indentation_spaces = 5
    /**
     *     foo
     */
  

• jsdocs_align_tags (String) Whether the words following the tags should align. Possible values are 'no', 'shallow' and 'deep'

  For backwards compatibility, false is equivalent to 'no', true is equivalent to 'shallow'

  'shallow' will align only the first words after the tag. eg:

    @param    {MyCustomClass} myVariable desc1
    @return   {String} foo desc2
    @property {Number} blahblah desc3
  

  'deep' will align each component of the tags, eg:

    @param    {MyCustomClass} myVariable desc1
    @return   {String}        foo        desc2
    @property {Number}        blahblah   desc3
  

• jsdocs_extra_tags (Array.String) An array of strings, each representing extra boilerplate comments to add to functions. These can also include arbitrary text (not just tags).

    // jsdocs_extra_tags = ['This is a cool function', '@author nickf', '@version ${1:[version]}']
    /**<<enter>>
    function foo (x) {}
  
    /**
     * [foo description]
     * This is a cool function
     * @author nickf
     * @version [version]
     * @param  {[type]} x [description]
     * @return {[type]}
     */
    function foo (x) {}
  

  Basic variable substitution is supported here for the variables date and datetime, wrapped in double curly brackets.

    // jsdocs_extra_tags = ['@date {{date}}', '@anotherdate {{datetime}}']
    /**<<enter>>
    function foo() {}
  
    /**
     * [foo description]
     * @date     2013-03-25
     * @datetime 2013-03-25T21:16:25+0100
     * @return   {[type]}
     */
  

• jsdocs_extra_tags_go_after (Boolean) If true, the extra tags are placed at the end of the block (after param/return). Default: false

• jsdocs_extend_double_slash (Boolean) Whether double-slash comments should be extended. An example of this feature is described above. Default: true

• jsdocs_deep_indent (Boolean) Whether pressing tab at the start of a line in docblock should indent to match the previous line's description field. An example of this feature is described above. Default: true

• jsdocs_notation_map (Array) An array of notation objects. Each notation object must define either a prefix OR a regex property, and a type property.

• jsdocs_return_tag (String) The text which should be used for a @return tag. By default, @return is used, however this can be changed to @returns if you use that style.

• jsdocs_spacer_between_sections (Boolean|String) If true, then extra blank lines are inserted between the sections of the docblock. If set to "after_description" then a spacer will only be added between the description and the first tag. Default: false.

• jsdocs_indentation_spaces_same_para (Number) Described above in the Reformatting paragraphs section. Default: 1

• jsdocs_autoadd_method_tag (Boolean) Add a @method tag to docblocks of functions. Default: false

• jsdocs_simple_mode (Boolean) If true, DocBlockr won't add a template when creating a doc block before a function or variable. Useful if you don't want to write Javadoc-style, but still want your editor to help when writing block comments. Default: false

• jsdocs_lower_case_primitives (Boolean) If true, primitive data types are added in lower case, eg "number" instead of "Number". Default: false

• jsdocs_short_primitives (Boolean) If true, the primitives Boolean and Integer are shortened to Bool and Int. Default: false

• jsdocs_newline_after_block (Boolean) If true, an extra line break is added after the end of a docblock to separate it from the code. Default false

• jsdocs_param_name (Boolean) If true, the name of a function parameter is added to the template. If false, it is omitted. Default: true

• jsdocs_decorate (Boolean) If false, disable decoration of single line comments with Ctrl+Enter. Default: true

• jsdocs_quick_open_inline (Boolean) If true, an inline docblock will be opened when pressing Space after an opener (/**). When set to false, these can be opened by pressing Shift+Enter. Default: true

• jsdocs_function_description (Boolean) If true, a 'description' line will be added for functions. Default: true

Contributors

This package was created by Nick Fisher, but has many contributions from others. Please take a look at the contributors list to see who else should get some thanks.