When working with JavaScript, we deal a lot with conditionals, here are the 5 tips for you to write better / cleaner conditionals.
在使用JavaScript时，我们会处理很多条件语句，这里有5个技巧可以帮助您编写更好、更简洁的条件语句。
1、Use Array.includes for Multiple Criteria（对多个条件使用Array.includes）
Let's take a look at the example below:
让我们看看下面的例子：
// conditionfunction test(fruit) { if (fruit == 'apple' || fruit == 'strawberry') { console.log('red');
}
}At first glance, the above example looks good. However, what if we get more red fruits, say cherry and cranberries? Are we going to extend the statement with more || ?
乍一看，上面的例子看起来不错。然而，如果我们得到更多的红色水果，比如樱桃和小红莓呢？我们要用更多的||来扩展这个表述吗？
We can rewrite the conditional above by using Array.includes (Array.includes)，Array.includes相关文档
我们可以用Array.includes重写上面的条件
function test(fruit) { // extract conditions to array
const redFruits = ['apple', 'strawberry', 'cherry', 'cranberries']; if (redFruits.includes(fruit)) { console.log('red');
}
}We extract the red fruits (conditions) to an array. By doing this, the code looks tidier.
我们将红色水果（条件）提取到一个数组中。这样做之后，代码看起来更整洁。
2、Less Nesting, Return Early（更少的嵌套，尽早返回）
Let's expand the previous example to include two more conditions:
让我们扩展前面的示例，以包含另外两个条件：
if no fruit provided, throw error
如果没有提供水果（名称），抛出错误。
accept and print the fruit quantity（n. 量，数量；大量；总量） if exceed（vt. 超过；胜过） 10.
如果（红色水果）数量超过10个，接受并打印。
function test(fruit, quantity) { const redFruits = ['apple', 'strawberry', 'cherry', 'cranberries']; // condition 1: fruit must has value
if (fruit) { // condition 2: must be red
if (redFruits.includes(fruit)) { console.log('red'); // condition 3: must be big quantity
if (quantity > 10) { console.log('big quantity');
}
}
} else { throw new Error('No fruit!');
}
}// test resultstest(null); // error: No fruitstest('apple'); // print: redtest('apple', 20); // print: red, big quantityLook at the code above, we have:
看看上面的代码，我们有：
1 if/else statement that filter out invalid condition
1组过滤无效条件的if/else语句。
3 levels of nested if statement (condition 1, 2 & 3)
3层的if嵌套语句（条件1、2和3）
A general rule I personally follow is return early when invalid conditions found.
我个人遵循的一般规则是，当发现无效条件时，提前返回。
/_ return early when invalid conditions found _/function test(fruit, quantity) { const redFruits = ['apple', 'strawberry', 'cherry', 'cranberries']; // condition 1: throw error early
if (!fruit) throw new Error('No fruit!'); // condition 2: must be red
if (redFruits.includes(fruit)) { console.log('red'); // condition 3: must be big quantity
if (quantity > 10) { console.log('big quantity');
}
}
}By doing this, we have one less level of nested statement. This coding style is good especially when you have long if statement (imagine you need to scroll to the very bottom to know there is an else statement, not cool).
这样，我们就少了一层嵌套。这种编码风格很好，尤其是当你有很长的if语句时（想象一下，你需要滚动到最底部才能知道还有一个else语句，这并不酷）。
We can further reduce the nesting if, by inverting the conditions & return early. Look at condition 2 below to see how we do it:
通过反转条件和提早返回，我们可以进一步减少嵌套。看看下面的条件2，我们是怎么做的：
/_ return early when invalid conditions found _/function test(fruit, quantity) { const redFruits = ['apple', 'strawberry', 'cherry', 'cranberries']; if (!fruit) throw new Error('No fruit!'); // condition 1: throw error early
if (!redFruits.includes(fruit)) return; // condition 2: stop when fruit is not red
console.log('red'); // condition 3: must be big quantity
if (quantity > 10) { console.log('big quantity');
}
}By inverting the conditions of condition 2, our code is now free of a nested statement. This technique is useful when we have long logic to go and we want to stop further process when a condition is not fulfilled.
通过反转条件2的条件，我们的代码现在没有嵌套语句。当我们有很长的逻辑要处理时，这种技术是有用的，当一个条件没有满足时，我们想要停止进一步的处理。
However, that's no hard rule for doing this. Ask yourself, is this version (without nesting) better / more readable than the previous one (condition 2 with nested)?
然而，这并不是严格的规则。问问自己，这个版本（没有嵌套）是否比前一个版本（嵌套的条件2）更好、更易读？
For me, I would just leave it as the previous version (condition 2 with nested). It is because:
对于我来说，我将把它保留为以前的版本（条件2和嵌套）。这是因为：
the code is short and straight forward, it is clearer with nested if
代码简短而直接，如果嵌套，代码就更清晰了
inverting condition may incur more thinking process (increase cognitive（adj.认知的；感知的；认识的） load)
反转条件可能会导致更多的思考过程（增加认知负荷）
Therefore, always aims for Less Nesting and Return Early but don't overdo it. There is an article & StackOverflow discussion that talks further on this topic if you interested:
因此，总是以更少的嵌套及尽早返回为目标，但不要过度。如果你感兴趣的话，StackOverflow有一篇相关的文章讨论了这个话题：
Avoid Else, Return Early by Tim Oxley
Tim Oxley的文章，避免Else，尽早返回
StackOverflow discussion on if/else coding style
StackOverflow基于if/else编码风格的讨论
3、Use Default Function Parameters and Destructuring（使用默认的函数参数和解构）
I guess the code below might look familiar to you, we always need to check for null / undefined value and assign default value when working with JavaScript:
我想下面的代码对您来说可能很熟悉，我们在使用JavaScript时总是需要检查null或undefined值并分配默认值:
function test(fruit, quantity) { if (!fruit) return; const q = quantity || 1; // if quantity not provided, default to one
console.log(`We have ${q} ${fruit}!`);
}//test resultstest('banana'); // We have 1 banana!test('apple', 2); // We have 2 apple!In fact, we can eliminate（vt. 消除；排除） the variable q by assigning default function parameters.
事实上，我们可以通过指定默认的函数参数来消除变量q。
function test(fruit, quantity = 1) { // if quantity not provided, default to one
if (!fruit) return; console.log(`We have ${quantity} ${fruit}!`);
}//test resultstest('banana'); // We have 1 banana!test('apple', 2); // We have 2 apple!Much easier & intuitive isn't it? Please note that each parameter can has it own default function parameter. For example, we can assign default value to fruit too: function test(fruit = 'unknown', quantity = 1).
更简单和直观，不是吗？请注意，每个参数都可以有自己的默认函数参数。例如，我们也可以为fruit赋值：function test(fruit = 'unknown'， quantity = 1)。
What if our fruit is an object? Can we assign default parameter?
如果我们的水果是一个对象呢？我们可以指定默认参数吗？
function test(fruit) { // printing fruit name if value provided
if (fruit && fruit.name) { console.log (fruit.name);
} else { console.log('unknown');
}
}//test resultstest(undefined); // unknowntest({ }); // unknowntest({ name: 'apple', color: 'red' }); // appleLook at the example above, we want to print the fruit name if it's available or we will print unknown. We can avoid the conditional fruit && fruit.name checking with default function parameter & destructing.
看看上面的例子，我们想打印水果名，如果它是可用的，或者我们将打印unknown。我们可以避免使用与默认函数参数和解构对条件fruit && fruit.name进行检查。
// destructing - get name property only// assign default empty object {}function test({name} = {}) { console.log (name || 'unknown');
}//test resultstest(undefined); // unknowntest({ }); // unknowntest({ name: 'apple', color: 'red' }); // appleSince we only need property name from fruit, we can destructure the parameter using {name}, then we can use name as variable in our code instead of fruit.name.
因为我们只需要水果中的属性name，所以我们可以使用{name}来解构，然后我们可以在代码中使用name作为变量，而不是fruit.name。
We also assign empty object {} as default value. If we do not do so, you will get error when executing the line test(undefined) - Cannot destructure property name of 'undefined' or 'null'. because there is no name property in undefined.
我们还将空对象{}指定为默认值。如果我们不这样做，当执行test(undefined)，不能解构undefined或null的属性名时，您将会得到错误。因为在undefined中没有name属性。
If you don't mind using 3rd party libraries, there are a few ways to cut down null checking:
如果您不介意使用第三方库，有一些方法可以减少null检查：
use Lodash get function
使用Lodash的get函数
use Facebook open source's idx library (with Babeljs)
使用Facebook的开源库idx（以及Babeljs）
Here is an example of using Lodash:
这是使用Lodash的例子：
// Include lodash library, you will get _function test(fruit) { console.log(__.get(fruit, 'name', 'unknown'); // get property name, if not available, assign default value 'unknown'}//test resultstest(undefined); // unknowntest({ }); // unknowntest({ name: 'apple', color: 'red' }); // appleYou may run the demo code here. Besides, if you are a fan of Functional Programming (FP), you may opt to use Lodash fp, the functional version of Lodash (method changed to get or getOr).
您可以在这里运行演示代码。此外，如果你喜欢函数式编程(FP)，你可以选择使用Lodash FP, Lodash的功能版本（方法改为get或getOr）。
4、Favor Map / Object Literal than Switch Statement（选择Map或对象字面量，而不是Switch语句）
Let's look at the example below, we want to print fruits based on color:
让我们看看下面的例子，我们想要基于颜色打印水果名称：
function test(color) { // use switch case to find fruits in color
switch (color) { case 'red': return ['apple', 'strawberry']; case 'yellow': return ['banana', 'pineapple']; case 'purple': return ['grape', 'plum']; default: return [];
}
}//test resultstest(null); // []test('yellow'); // ['banana', 'pineapple']The above code seems nothing wrong, but I find it quite verbose. The same result can be achieve with object literal with cleaner syntax:
上面的代码似乎没有什么问题，但我发现它相当冗长。同样的结果可以通过对象字面量和更简洁的语法来实现：
// use object literal to find fruits in color
const fruitColor = { red: ['apple', 'strawberry'], yellow: ['banana', 'pineapple'], purple: ['grape', 'plum']
};function test(color) { return fruitColor[color] || [];
}Alternatively（adv. 非此即彼；二者择一地；作为一种选择）, you may use Map to achieve the same result:
或者，可以使用Map来实现相同的结果：
// use Map to find fruits in color
const fruitColor = new Map()
.set('red', ['apple', 'strawberry'])
.set('yellow', ['banana', 'pineapple'])
.set('purple', ['grape', 'plum']);function test(color) { return fruitColor.get(color) || [];
}Map is the object type available since ES2015, allow you to store key value pair.
Map是ES2015以后可用的对象类型，允许您存储键值对。
Should we ban the usage of switch statement? Do not limit yourself to that. Personally, I use object literal whenever possible, but I wouldn't set hard rule to block that, use whichever make sense for your scenario.
我们应该禁止使用switch语句吗？不要把自己局限于此。就我个人而言，我尽可能地使用对象字面量，但是我不会设置严格的规则来阻止它，使用对您的场景有意义的任何一个。
Todd Motto has an article that dig deeper on switch statement vs object literal, you may read here.
Todd Motto有一篇文章深入讨论switch语句与对象字面量，你可以在这里阅读。
TL;DR; Refactor the syntax
For the example above, we can actually refactor our code to achieve the same result with Array.filter.
对于上面的示例，我们实际上可以重构代码，以使用Array.filter获得相同的结果。
const fruits = [
{ name: 'apple', color: 'red' },
{ name: 'strawberry', color: 'red' },
{ name: 'banana', color: 'yellow' },
{ name: 'pineapple', color: 'yellow' },
{ name: 'grape', color: 'purple' },
{ name: 'plum', color: 'purple' }
];function test(color) { // use Array filter to find fruits in color
return fruits.filter(f => f.color == color);
}There's always more than 1 way to achieve the same result. We have shown 4 with the same example. Coding is fun!
总有不止一种方法可以达到同样的效果。我们展示了4个相同效果的例子。编码是有趣的！
5、Use Array.every & Array.some for All / Partial Criteria（所有或部分使用Array.every & Array.some的条件）
This last tip is more about utilizing（v. 利用） new (but not so new) Javascript Array function to reduce the lines of code. Look at the code below, we want to check if all fruits are in red color:
最后一个技巧是关于使用新的（但不是很新）Javascript数组函数来减少代码行。看看下面的代码，我们想检查所有的水果是否都是红色的:
const fruits = [
{ name: 'apple', color: 'red' },
{ name: 'banana', color: 'yellow' },
{ name: 'grape', color: 'purple' }
];function test() { let isAllRed = true; // condition: all fruits must be red
for (let f of fruits) { if (!isAllRed) break;
isAllRed = (f.color == 'red');
} console.log(isAllRed); // false}The code is so long! We can reduce the number of lines with Array.every:
代码太长了！我们可以用Array.every来减少行数：
const fruits = [
{ name: 'apple', color: 'red' },
{ name: 'banana', color: 'yellow' },
{ name: 'grape', color: 'purple' }
];function test() { // condition: short way, all fruits must be red
const isAllRed = fruits.every(f => f.color == 'red'); console.log(isAllRed); // false}Much cleaner now right? In a similar way, if we want to test if any of the fruit is red, we can use Array.some to achieve it in one line.
现在干净多了，对吧？类似地，如果我们想测试任何一个水果是红色的，我们可以使用Array.some来实现它在一行。
const fruits = [
{ name: 'apple', color: 'red' },
{ name: 'banana', color: 'yellow' },
{ name: 'grape', color: 'purple' }
];function test() { // condition: if any fruit is red
const isAnyRed = fruits.some(f => f.color == 'red'); console.log(isAnyRed); // true}
作者：MrDcheng
链接：https://www.jianshu.com/p/d5acd5f52db8