JS-0239 @ afc51f6 • Snowtrack / SnowFS

Run summary

2 years ago

cce7004..afc51f6

33 s

Consider using let or const instead of var JS-0239

Anti-pattern

Major

3 occurrences in this check

Unexpected var, use let or const instead

main.ts

542          }
543        }
544
545        var cur_commit: Commit = {};546        process.stdout.write(JSON.stringify(o, (key, value) => {
547          if (value instanceof Commit) {
548            cur_commit = value;

Unexpected var, use let or const instead

main.ts

533        
534        if (opts.changedFiles) {
535          var statuses = {};
536          var commit_prev = commits[0];537          for (const commit of commits.slice(1)) {
538            const diff = new Diff(commit_prev, commit, { includeDirs: true });
539

Unexpected var, use let or const instead

main.ts

532        const o = { commits, refs, head: repo.getHead().isDetached() ? headHash : headName };
533        
534        if (opts.changedFiles) {
535          var statuses = {};536          var commit_prev = commits[0];
537          for (const commit of commits.slice(1)) {
538            const diff = new Diff(commit_prev, commit, { includeDirs: true });

Description

It is recommended to use let or const over var. This will help prevent re-declaration of variables that are in the global scope when using var.

ES6 allows programmers to create variables with block scope instead of function scope using the let and const keywords. Block scope is common in many other programming languages and helps programmers avoid mistakes such as this one:

var count = people.length;
var enoughFood = count > sandwiches.length;

if (enoughFood) {
    var count = sandwiches.length; // accidentally overriding the count variable
    console.log("We have " + count + " sandwiches for everyone. Plenty for all!");
}

// our count variable is no longer accurate
console.log("We have " + count + " people and " + sandwiches.length + " sandwiches!");

Block scoped variables shadow outer declarations instead of writing to them.

NOTE: There are certain edge cases where users might want to consider var. Consider this example:

var lib = lib || { run: () => {} }

Here, lib might be a library that is exposed to an HTML file using a <script> tag. The var keyword helps avoid re-writing lib if it has already been declared via an injected script that was executed before this one. Ideally, you should let bundlers worry about cases like this. But if you want to use var anyway, consider using a skipcq comment, or disabling the issue altogether.

Bad Practice

var x = "y";
var CONFIG = {};

Snowtrack / snowfs

Bad Practice

Recommended