Created
October 8, 2012 10:02
-
-
Save couto/3851777 to your computer and use it in GitHub Desktop.
DocBlockr Configuration
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
{ | |
// If true, when in a docblock, pressing tab after a @tag line (like @param, @return) | |
// will indent to the description. This is useful if you are writing a long description | |
// and want that block of text to stay aligned. | |
"jsdocs_deep_indent": true, | |
// If true, then pressing enter while in a double-slash comment (like this one) | |
// will automatically add two slashes to the next line as well | |
"jsdocs_extend_double_slash": true, | |
// the number of spaces to add after the leading * | |
"jsdocs_indentation_spaces": 1, | |
// whether the words following the @tags should align. | |
// Possible values are 'no', 'shallow', 'deep' | |
// For backwards compatibility, false is equivalent to 'no', true is equivalent to 'shallow' | |
// | |
// 'shallow' will just align 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_align_tags": "deep", | |
// Any additional boilerplate tags which should be added to each block. Should be an array of strings. | |
// Note that this only applies when a docblock is opened directly preceding a function. | |
// Tab points can be added by using snippet syntax, eg: ${1:default text} | |
"jsdocs_extra_tags": ["${1:@method}"], | |
// A map to determine the value of variables, should hungarian notation (or similar) be in use | |
"jsdocs_notation_map": [{ | |
"regex": "^_(?=_)", | |
"tags": ["@${1:private}"] | |
},{ | |
"regex": "^_(?!_)", | |
"tags": ["@${1:protected}"] | |
},{ | |
"regex": "^(?!_)", | |
"tags" : ["@${1:public}"] | |
}], | |
// Since there seems to be no agreed standard for "@return" or "@returns", use this setting to rename it as you wish. | |
"jsdocs_return_tag": "@returns", | |
// Add a '[description]' placeholder for the return tag? | |
"jsdocs_return_description": true, | |
// Whether there should be blank lines added between the description line, and between tags of different types. | |
// If true, the output might look like this: | |
// | |
// /** | |
// * [description] | |
// * | |
// * @param {String} foo | |
// * @param {Number} bar | |
// * | |
// * @return {[Type]} | |
// */ | |
"jsdocs_spacer_between_sections": false, | |
// Whether each section should be indented to the same level, or indent each one individually. | |
// (When true, the @param section will lose the extra space immediately after each '@param'). | |
"jsdocs_per_section_indent": false | |
} |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment