脚本宝典收集整理的这篇文章主要介绍了谷歌JavaScript风格指南中值得注意的13点，脚本宝典觉得挺不错的，现在分享给大家，也给大家做个参考。对于那些不熟悉JavaScript的人来说，GOOGLE提供了一个编写JavaScript的样式指南，该指南列出了（Google相信的）编写干净、易懂的代码的最佳风格实践。 这些不是编写有效JavaScript的硬性规则，而是在整个源文件中维护一致和吸引人的样式选择的限制。这对于JavaScript尤其有趣，JavaScript是一种灵活宽容的语言，允许各种各样的样式选择。 谷歌和airbnb有两个最流行的风格指南在那里。如果你花很多时间写JS，我绝对建议你检查一下。 以下是我认为谷歌JS风格指南中最有趣和相关的十三条规则。 它们处理从激烈争论的问题（选项卡与空格，以及如何使用分号的有争议的问题）到让我吃惊的一些更模糊的规范。他们肯定会改变我写JS的方式。 对于每个规则，我将给出规范的概要，后面是详细描述规则的样式指南中的支持引号。在适用的情况下，我还将提供实践中的样式的示例，并将其与不遵循规则的代码进行比较。 使用空格，不使用制表符 除了行结束符序列之外，ASCII水平空格字符（0x20）是源文件中任何地方出现的唯一空格字符。这意味着……标签字符不用于缩进。 指南稍后指定您应该使用两个空格（不是四）来缩进。 For anyone who isn’t already familiar wITh it, Google puts out a style guide for writing JavaScript that lays out (what Google believes to be) the best stylistic PRactices for writing clean, understandable code. These are not hard and fast rules for writing valid JavaScript, only proscriptions for maintaining consistent and apPEaling style choices throughout your source files. This is particularly interesting for JavaScript, which is a flexible and forgiving language that allows for a wide VARiety of stylistic choices. Google and Airbnb have two of the most popular style guides out there. I’d definitely recommend you check out both of them if you spend much time writing JS. The following are thirteen of what I think are the most interesting and relevant rules From Google’s JS Style Guide. They deal with everything from hotly contested issues (tabs versus spaces, and the controversial issue of how SEMicolons should be used), to a few more obscure specifications which surprised me. They will definitely change the way I write my JS going forward. For each rule, I’ll give a summary of the specification, followed by a supporting quote from the style guide that describes the rule in detail. Where applicable, I’ll also provide an example of the style in practice, and contrast it with code that does not follow the rule. Use spaces, not tabs Aside from the line terminator sequence, the ASCII horizontal space character (0x20) is the only whitespace character that appears anywhere in a source file. This implies that… Tab characters are not used for indentation. The guide later specifies you should use two spaces (not four) for indentation.
// bad
function foo() {
∙∙∙∙let name;
}
// bad
function bar() {
∙let name;
}
// good
function baz() {
∙∙let name;
}// bad
let luke = {}
let leia = {}
[luke, leia].forEach(jedi => jedi.father = 'vader')
// good
let luke = {};
let leia = {};
[luke, leia].forEach((jedi) => {
jedi.father = 'vader';
});// Don't do this kind of thing yet:
//------ lib.js ------
export function square(x) {
return x * x;
}
export function diag(x, y) {
return sqrt(square(x) + square(y));
}// bad
{
tiny: 42,
longer: 435,
};
// good
{
tiny: 42,
longer: 435,
};// bad
var example = 42;
// good
let example = 42;// bad
[1, 2, 3].map(function (x) {
const y = x + 1;
return x * y;
});
// good
[1, 2, 3].map((x) => {
const y = x + 1;
return x * y;
});// bad
function sayHi(name) {
return 'How are you, ' + name + '?';
}
// bad
function sayHi(name) {
return ['How are you, ', name, '?'].join();
}
// bad
function sayHi(name) {
return `How are you, ${ name }?`;
}
// good
function sayHi(name) {
return `How are you, ${name}?`;
}// bad (sorry, this doesn't show up well on mobile)
const longString = 'This is a very long string that \
far exceeds the 80 column limit. It unfortunately \
contains long stretches of spaces due to how the \
continued lines are indented.';
// good
const longString = 'This is a very long string that ' +
'far exceeds the 80 column limit. It does not contain ' +
'long stretches of spaces since the concatenated ' +
'strings are cleaner.';// bad
let obj = { a: 20, b: 30 };
let propName = getPropName(); // returns "a" or "b"
eval( 'var result = obj.' + propName );
// good
let obj = { a: 20, b: 30 };
let propName = getPropName(); // returns "a" or "b"
let result = obj[ propName ]; // obj[ "a" ] is the same as obj.a// bad
const number = 5;
// good
const NUMBER = 5;
One variable per declaration
Every local variable declaration declares only one variable: declarations such as let a = 1, b = 2; are not used.
// bad
let a = 1, b = 2, c = 3;
// good
let a = 1;
let b = 2;
let c = 3;// bad
let directive = "No identification of self or mission."
// bad
let saying = 'Say it ain\u0027t so.';
// good
let directive = 'No identification of self or mission.';
// good
let saying = `Say it ain't so`;以上是脚本宝典为你收集整理的谷歌JavaScript风格指南中值得注意的13点全部内容，希望文章能够帮你解决谷歌JavaScript风格指南中值得注意的13点所遇到的问题。
本图文内容来源于网友网络收集整理提供，作为学习参考使用，版权属于原作者。
如您有任何意见或建议可联系处理。小编QQ：384754419，请注明来意。