Software Style Guide


Converse.js doesn’t yet use any of the new ES2015 features, because we don’t rely on a transpiler and still support older browsers.

Most of the style guide recommendations here come from Douglas Crockford’s book JavaScript, the good parts

This style guide is fairly opinionated. Some of these opinions perhaps don’t conform to your expectations on how JavaScript code should look like. I apologize for that. However, for the sake of sanity, consistency and having code that is pleasing to the eye, please stick to these guidelines.

Tabs or spaces?

We always indent 4 spaces. Proper indentation is very important for readability.

Underscores or camelCase?

We use camelCase for function names and underscores for variables names.

For example:

function thisIsAFunction () {
    var this_is_a_variable;

Spaces around operators

In general, spaces are put around operators, such as the equals = or plus + signs.

For example:

if (sublocale != locale) {
    // do something

An exception is when they appear inside for-loop expressions, for example:

for (i=0; i<msgs_length; i++) {
    // do something

Generally though, rather err on the side of adding spaces, since they make the code much more readable.

Constants are written in ALL_CAPS

Identifiers that denote constant values should be written in all capital letters, with underscores between words.

For example:

var SECONDS_IN_HOUR = 3600;
var seconds_since_message = 0;

Function declaration and invocation

When declaring a function, the function name and the brackets after it are separated with a space. Like so:

function update (model) { = 'bar';

When calling the same function, the brackets are written without a space in between:


This is to make a more explicit visual distinction between method declarations and method invocations.

Checking for equality

JavaScript has a strict === and less strict == equality operator. The stricter equality operator also does type checking. To avoid subtle bugs when doing comparisons, always use the strict equality check.

Curly brackets

Curly brackets must appear on the same lines as the if and else keywords. The closing curly bracket appears on its own line.

For example:

if (locales[locale]) {
    return locales[locale];
} else {
    sublocale = locale.split("-")[0];
    if (sublocale != locale && locales[sublocale]) {
        return locales[sublocale];

Always enclose blocks in curly brackets

When writing an a block such as an if or while statement, always use curly brackets around that block of code. Even when not strictly required by the compiler (for example if its only one line inside the if statement).

For example, like this:

if (condition === true) {

and NOT like this:

if (converse.auto_list_rooms)

This is to aid in readability and to avoid subtle bugs where certain lines are wrongly assumed to be executed within a block.