HTML tutorial
CSS3 tutorial
Bootstrap tutorial
JavaScript tutorial
JQuery tutorial
AngularJS tutorial
React tutorial
NodeJS tutorial
PHP tutorial
Python tutorial
Python3 tutorial
Django tutorial
Linux tutorial
Docker tutorial
Ruby tutorial
Java tutorial
C tutorial
C ++ tutorial
Perl tutorial
JSP tutorial
Lua tutorial
Scala tutorial
Go tutorial
ASP.NET tutorial
C # tutorial
This chapter points out some common JavaScript mistakes
JavaScript programs may generate unexpected results if a programmer
accidentally uses an assignment operator (=
), instead of a comparison operator
(==
) in an if statement.
This if
statement returns false
(as
expected) because x is
not equal to 10:
let x = 0;
if (x == 10)
This if
statement returns true
(maybe not
as expected), because 10 is
true:
let x = 0;
if (x = 10)
This if
statement returns false
(maybe not
as expected), because 0 is
false:
let x = 0;
if (x = 0)
An assignment always returns the value of the assignment.
In regular comparison, data type does not matter. This if
statement returns
true:
let x = 10;
let y = "10";
if (x == y)
In strict comparison, data type does matter. This if
statement returns false:
let x = 10;
let y = "10";
if (x === y)
It is a common mistake to forget that switch
statements use strict
comparison:
This case switch
will display an alert:
let x = 10;
switch(x) {
case 10: alert("Hello");
}
This case switch
will not display an alert:
let x = 10;
switch(x) {
case "10": alert("Hello");
}
In JavaScript both operations use the same +
operator.
Because of this, adding a number as a number will produce a different result from adding a number as a string:
let x = 10;
x = 10 + 5; //
Now x is 15
let y = 10;
y += "5";
// Now y is "105"
When adding two variables, it can be difficult to anticipate the result:
let x = 10;
let y = 5;
let z = x + y; // Now z is 15
let x = 10;
let y = "5";
let z = x + y; // Now z is "105"
All numbers in JavaScript are stored as 64-bits Floating point numbers (Floats).
All programming languages, including JavaScript, have difficulties with precise floating point values:
let x = 0.1;
let y = 0.2;
let z = x + y
// the result in z will not be 0.3
To solve the problem above, it helps to multiply and divide:
let z = (x * 10 + y * 10) / 10; // z will be 0.3
JavaScript will allow you to break a statement into two lines:
let x =
"Hello World!";
But, breaking a statement in the middle of a string will not work:
let x = "Hello
World!";
You must use a "backslash" if you must break a statement in a string:
let x = "Hello \
World!";
Because of a misplaced semicolon, this code block will execute regardless of the value of x:
if (x == 19);
{
// code block
}
It is a default JavaScript behavior to close a statement automatically at the end of a line.
Because of this, these two examples will return the same result:
function myFunction(a) {
let power = 10
return a * power
}
function myFunction(a) {
let power = 10;
return a * power;
}
JavaScript will also allow you to break a statement into two lines.
Because of this, example 3 will also return the same result:
function myFunction(a) {
let
power = 10;
return a * power;
}
But, what will happen if you break the return statement in two lines like this:
function myFunction(a) {
let
power = 10;
return
a * power;
}
The function will return undefined
!
Why? Because JavaScript thought you meant:
function myFunction(a) {
let
power = 10;
return;
a * power;
}
If a statement is incomplete like:
let
JavaScript will try to complete the statement by reading the next line:
power = 10;
But since this statement is complete:
return
JavaScript will automatically close it like this:
return;
This happens because closing (ending) statements with semicolon is optional in JavaScript.
JavaScript will close the return statement at the end of the line, because it is a complete statement.
Never break a return statement.
Many programming languages support arrays with named indexes.
Arrays with named indexes are called associative arrays (or hashes).
JavaScript does not support arrays with named indexes.
In JavaScript, arrays use numbered indexes:
const person = [];
person[0] = "John";
person[1] = "Doe";
person[2] = 46;
person.length;
// person.length will return 3
person[0];
// person[0] will return "John"
In JavaScript, objects use named indexes.
If you use a named index, when accessing an array, JavaScript will redefine the array to a standard object.
After the automatic redefinition, array methods and properties will produce undefined or incorrect results:
const person = [];
person["firstName"] = "John";
person["lastName"] = "Doe";
person["age"] = 46;
person.length; // person.length will
return 0
person[0];
// person[0] will return undefined
Trailing commas in object and array definition are legal in ECMAScript 5.
person = {firstName:"John", lastName:"Doe", age:46,}
points = [40, 100, 1, 5, 25, 10,];
WARNING !!
Internet Explorer 8 will crash.
JSON does not allow trailing commas.
person = {"firstName":"John", "lastName":"Doe", "age":46}
points = [40, 100, 1, 5, 25, 10];
JavaScript objects, variables, properties, and methods can be undefined
.
In addition, empty JavaScript objects can have the value null
.
This can make it a little bit difficult to test if an object is empty.
You can test if an object exists by testing if the type is undefined
:
if (typeof myObj === "undefined")
But you cannot test if an object is null
, because this will throw an error if the
object is undefined
:
if (myObj === null)
To solve this problem, you must test if an object is not null
,
and not undefined
.
But this can still throw an error:
if (myObj !== null && typeof myObj
!== "undefined")
Because of this, you must test for not undefined
before you can
test for not null
:
if (typeof myObj !== "undefined" && myObj !== null)