1 SC2288

Vidar Holen edited this page 2021-06-05 18:52:08 -07:00

Table of Contents

• This is interpreted as a command name ending with apostrophe. Double check syntax.
• Problematic code:
• Correct code:
• Rationale:
• Exceptions:
• Related resources:

This is interpreted as a command name ending with apostrophe. Double check syntax.

(also applies to multiple other characters like .,([{<>}])#"')

Problematic code:

var=$("wget 'http://www.shellcheck.net/'")
echo Usage: $0 {start|stop|restart}
array=val1, val2, val3

Correct code:

var="$(wget 'http://www.shellcheck.net/')"
echo "Usage: $0 {start|stop|restart}"
array=(val1 val2 val3)

Rationale:

ShellCheck found a command name ending with a symbol, such as a comma, parenthesis, quote, or similar. This is almost always due to a syntax issue in the script.

In the examples, bad quoting and invalid array syntax caused the shell to try to run commands ending in apostrophe, curly brace, and comma, respectively.

Exceptions:

If you have a command that does end in a symbol, you can ignore this message.

Related resources:

• Help by adding links to BashFAQ, StackOverflow, man pages, POSIX, etc!

ShellCheck

• Installation

  • CentOS6
  • More Installation Guides

• Usage

  • Directive
  • Ignore

• Integrating and extending

  • Misc. contributions
  • Azure Pipelines
  • Buildkite
  • CircleCI
  • DevGuide
  • Integration
  • JUnit
  • Phabricator
  • TravisCI
  • GitLab CI
  • Drone
  • GitHub Actions

• Severity

• Template

Each individual ShellCheck warning has its own wiki page like SC1000. Use GitHub Wiki's "Pages" feature above to find a specific one, or see Checks.