Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Put a hardline between "StringLiteral" + "StringLiteral"

See original GitHub issue

Right now

    console.error(
      'In order to use ' + prompt + ', you need to configure a ' +
      'few environment variables to be able to commit to the ' +
      'repository. Follow those steps to get you setup:\n' +
      '\n' +
      'Go to https://github.com/settings/tokens/new\n' +
      ' - Fill "Token description" with "' + prompt + ' for ' +
        repoSlug + '"\n' +
      ' - Check "public_repo"\n' +
      ' - Press "Generate Token"\n' +
      '\n' +
      'In a different tab, go to https://travis-ci.org/' +
        repoSlug + '/settings\n' +
      ' - Make sure "Build only if .travis.yml is present" is ON\n' +
      ' - Fill "Name" with "GITHUB_USER" and "Value" with the name of the ' +
        'account you generated the token with. Press "Add"\n' +
      '\n' +
      'Once this is done, commit anything to the repository to restart ' +
        'Travis and it should work :)'
    );

gets printed as

    console.error(
      "In order to use " +
        prompt +
        ", you need to configure a " +
        "few environment variables to be able to commit to the " +
        "repository. Follow those steps to get you setup:\n" +
        "\n" +
        "Go to https://github.com/settings/tokens/new\n" +
        ' - Fill "Token description" with "' +
        prompt +
        " for " +
        repoSlug +
        '"\n' +
        ' - Check "public_repo"\n' +
        ' - Press "Generate Token"\n' +
        "\n" +
        "In a different tab, go to https://travis-ci.org/" +
        repoSlug +
        "/settings\n" +
        ' - Make sure "Build only if .travis.yml is present" is ON\n' +
        ' - Fill "Name" with "GITHUB_USER" and "Value" with the name of the ' +
        'account you generated the token with. Press "Add"\n' +
        "\n" +
        "Once this is done, commit anything to the repository to restart " +
        "Travis and it should work :)"
    );

which breaks on every single + which makes the code harder to read.

One pattern that we can extract is that if you have “string” + “string”, it likely means that there was a \n there originally. So, if we would reformat the code as

group("In order to use " + prompt + ", you need to configure a " +)
group("few environment variables to be able to commit to the " +)
group("repository. Follow those steps to get you setup:\n" +)
group("\n" +)
group("Go to https://github.com/settings/tokens/new\n" +)
group(' - Fill "Token description" with "' + prompt + " for " + repoSlug + '"\n' +)
group(' - Check "public_repo"\n' +)
group(' - Press "Generate Token"\n' +)
group("\n" +)
group("In a different tab, go to https://travis-ci.org/" + repoSlug + "/settings\n" +)
group(' - Make sure "Build only if .travis.yml is present" is ON\n' +)
group(' - Fill "Name" with "GITHUB_USER" and "Value" with the name of the ' +)
group('account you generated the token with. Press "Add"\n' +)
group("\n" +)
group("Once this is done, commit anything to the repository to restart " +)
group("Travis and it should work :)")

that would lead to a better output than breaking on every single +