Linters are tools that can automatically check the style of your code and make improving suggestions. Then you can browse other style guides to pick up more ideas and decide which one you like best. If you’re a novice developer, start with the cheat sheet at the beginning of this chapter. There are many existing guides to choose from. Of course, a team can always write their own style guide, but usually there’s no need to. When all members of a team use the same style guide, the code looks uniform, regardless of which team member wrote it. which quotes to use, how many spaces to indent, the maximal line length, etc. Style GuidesĪ style guide contains general rules about “how to write” code, e.g. Then, maybe we won’t need to read the functions at all, especially if their names are descriptive of what they actually do. If the code goes first, then it becomes clear from the start. That’s because when reading code, we first want to know what it does. Most of time, the second variant is preferred. Mixed: a function is declared where it’s first used.
Try to avoid nesting code too many levels deep.įor example, in the loop, it’s sometimes a good idea to use the continue directive to avoid extra nesting.įor example, instead of adding a nested if conditional like this: The majority of developers put semicolons. Otherwise, it’s best to use semicolons to avoid possible pitfalls. If you’re an experienced JavaScript programmer, you may choose a no-semicolon code style like StandardJS. See more about that in the chapter Code structure. In JavaScript, though, there are cases where a line break is not interpreted as a semicolon, leaving the code vulnerable to errors. There are languages where a semicolon is truly optional and it is rarely used. There should not be more than nine lines of code without a vertical indentation.Ī semicolon should be present after each statement, even if it could possibly be skipped. Insert an extra newline where it helps to make the code more readable.
0 kommentar(er)
