Code-style for showdown and related projects.
In this file, you can check the the code styling, rules and commit message convetions for showdown and it's related projects. It's roughly based on Google JavaScript Style Guide and AngularJS Git Commit Msg Convention. Using these rules is strongly advisable when contributing to showdown projects. In this repository you can also find a .editorconfig, .jshintrc and .jscs.json file that you can use to automatically enforce these rules (if your IDE supports it).
For more information, check the editorconfig, jshint and jscs project pages.
- DO NOT USE tab character, use spaces instead
- Tab size is 2 spaces
- Indentation is 1 tab size (2 spaces)
- Continuation indent is 1 tab size
- Multiple variable declaration MUST BE chopped and aligned (4 spaces, usually)
- Empty lines MUST not keep indents
- Blank lines CAN be added for readability
- 2 consecutive blank lines are allowed
- 'case' branches in switch statements MUST BE indented
function foo() {
var bar = 'bar',
baz = 1;
if (bar === 'bar') {
alert('something');
}
}- Statements must ALWAYS be terminated with semicolon. However, multiple variable declaration is allowed.
- Single quotes are preferred to double quotes. Exceptionally, double quotes might be used if single quotes would require escaping
var foo = 'some string',
baz = "I'm using single quotes inside";- DO NOT ADD before:
- function declaration
- function call
function foo() {
return 0;
}
foo();- ADD before:
- 'if'
- 'for'
- 'while'
- 'switch'
- 'catch'
- in function expression
if (i > 10) {
for (var j = 0; j < 10; j++) {
switch (j) {
case 0:
value = 'zero';
break;
case 1:
value = 'one';
break;
}
}
}- ADD around:
- assignment operators (=, +=, ...)
- logical operators (&&, ||)
- equality operators (==, ===, !=, !==)
- relational operators (<, >, <=, >=)
- bitwise operators (&, |, ^, ...)
- additive operators (+, -) and multiplication operators (*,/,%)
- shift operators (<<,>>,>>>, ...)
var a = 0,
b = (i == j || j > 5),
c = (j << 2) & 4,
d += 1,
e = a + d;- DO NOT ADD around:
- unary operators (!, -, +, ++, --)
j++;
bar = !foo;- ADD before:
- function
- 'if'
- 'else'
- 'for'
- 'while'
- 'do'
- 'switch'
- 'try'
- 'catch'
- 'finally'
- ADD before:
- 'else'
- 'while'
- 'catch'
- 'finally'
var foo = function () {
if (bar) {
try {
baz();
} catch (e) {
alert('Failure: ' + e.message);
} finally {
reset(a, i);
}
} else {
bazinga();
}
}- DO NOT ADD within:
- brackets
- object literal braces
- function call, function declaration, 'if', 'for', 'while', 'switch' or 'catch' parentheses
- ADD
- before '?'
- after '?'
- before ':'
- after ':'
var c = j > 5 ? 'GT 5' : 'LE 5';- ADD
- after comma
- after property name-value separator (:)
- DO NOT ADD
- before comma
- before semicolon
- before property name-value separator (:)
We use egyptian braces. That means braces are ALWAYS placed at the End of Line Also, braces are required in every block elements, even if they are oneliners ('if', 'while', 'do...while', 'try...catch...finally', etc...)
We use a soft wrap of 120 characters long. Also:
- Comments MAY wrap at right margin
- Function declaration arguments MAY wrap if long and aligned when multiline.
- Function call arguments MAY wrap if long and aligned when multiline.
- Object literals MUST ALWAYS BE chopped
- Multiple variable declaration MUST BE chopped and aligned (4 spaces, usually)
foo(a, b, c, d); // Line comment
// which can be
// wrapped if
// long.
foo(a, b, c, d
e, f, g, h, i);
function foo(a, b, c, d, bla,
ble, bli, blu) {
}We use the AngularJS Git Commit Msg Convention because it enables us to:
- automatically generate the changelog with pointers to the appropriate issues and commits
- simple navigatie through the git history, focusing on important things while ignoring trivial changes
<type>(<scope>): <subject>
<body>
<footer>First line cannot be longer than 70 characters, second line is always blank and other lines should be wrapped at 80 characters. The type and scope should always be lowercase as shown below.
- feat (new feature for the user, not a new feature for build script)
- fix (bug fix for the user, not a fix to a build script)
- docs (changes to the documentation)
- style (formatting, missing semi colons, etc; no production code change)
- refactor (refactoring production code, eg. renaming a variable)
- test (adding missing tests, refactoring tests; no production code change)
- chore (updating grunt tasks etc; no production code change)
- list-parser
- loader
- extension-registering
- showdown-options
- etc.
The <scope> can be empty (eg. if the change is a global or difficult
to assign to a single component), in which case the parentheses are
omitted.
- uses the imperative, present tense: “change” not “changed” nor “changes”
- includes motivation for the change and contrasts with previous behavior
For more info about message body, see:
- http://365git.tumblr.com/post/3308646748/writing-git-commit-messages
- http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
Closed issues should be listed on a separate line in the footer prefixed with "Closes" keyword like this:
Closes #234or in case of multiple issues:
Closes #123, #245, #992All breaking changes have to be mentioned in footer with the description of the change, justification and migration notes.
BREAKING CHANGE:
`extension-registering` now is done throught a function call instead of assigning a property directly in the `showdown.extensions` object.
To migrate your extension, use the function showdown.registerExtension() instead.For more information and examples, please read the AngularJS Git Commit Msg Convention.