View GitHub Repository jaxon-dialogs

Schedule Inspection
Subscribe

templates/overhang/alert.js   A
last analyzed

↳ Parent: Project

Complexity

Total Complexity 8
Complexity/F 1.33

Size

Lines of Code 26
Function Count 6

Duplication

Duplicated Lines 0
Ratio 0 %

Importance

Changes 0
Metric Value
eloc 18
c 0
b 0
f 0
dl 0
loc 26
rs 10
wmc 8
mnd 2
bc 2
fnc 6
bpm 0.3333
cpm 1.3333
noi 4
1 
jaxon.dialogs.overhang = {
0 ignored issues
– show
Bug introduced by
The variable jaxon seems to be never declared. If this is a global, consider adding a /** global: jaxon */ comment.

This checks looks for references to variables that have not been declared. This is most likey a typographical error or a variable has been renamed.

To learn more about declaring variables in Javascript, see the MDN.

Loading history...
2 
    success: function(content, title) {
3 
        $("body").overhang({message: content, title: title, type: 'success', duration: 5});
4 
    },
5 
    info: function(content, title) {
6 
        $("body").overhang({message: content, title: title, type: 'info', duration: 5});
7 
    },
8 
    warning: function(content, title) {
9 
        $("body").overhang({message: content, title: title, type: 'warn', duration: 5});
10 
    },
11 
    error: function(content, title) {
12 
        $("body").overhang({message: content, title: title, type: 'error', duration: 5});
13 
    },
14 
    confirm: function(question, title, yesCallback, noCallback) {
15 
        $("body").overhang({
16 
            type: "confirm",
17 
            message: question,
18 
            callback: function(res){
19 
                if(res)
20 
                    yesCallback();
0 ignored issues
– show
Coding Style Best Practice introduced by
Curly braces around statements make for more readable code and help prevent bugs when you add further statements.

Consider adding curly braces around all statements when they are executed conditionally. This is optional if there is only one statement, but leaving them out can lead to unexpected behaviour if another statement is added later.

Consider:

if (a > 0)
    b = 42;

If you or someone else later decides to put another statement in, only the first statement will be executed.

if (a > 0)
    console.log("a > 0");
    b = 42;

In this case the statement b = 42 will always be executed, while the logging statement will be executed conditionally.

if (a > 0) {
    console.log("a > 0");
    b = 42;
}

ensures that the proper code will be executed conditionally no matter how many statements are added or removed.

Loading history...
21 
                else if(noCallback != undefined)
0 ignored issues
– show
Best Practice introduced by
Comparing noCallback to undefined using the != operator is not safe. Consider using !== instead.
Loading history...
22 
                    noCallback();
0 ignored issues
– show
Coding Style Best Practice introduced by
Curly braces around statements make for more readable code and help prevent bugs when you add further statements.

Consider adding curly braces around all statements when they are executed conditionally. This is optional if there is only one statement, but leaving them out can lead to unexpected behaviour if another statement is added later.

Consider:

if (a > 0)
    b = 42;

If you or someone else later decides to put another statement in, only the first statement will be executed.

if (a > 0)
    console.log("a > 0");
    b = 42;

In this case the statement b = 42 will always be executed, while the logging statement will be executed conditionally.

if (a > 0) {
    console.log("a > 0");
    b = 42;
}

ensures that the proper code will be executed conditionally no matter how many statements are added or removed.

Loading history...
23 
            }
24 
        });
25 
    }
26 
};
27