2 SC2276

Joachim Ansorg edited this page 2021-11-12 19:58:23 +01:00

Table of Contents

• This is interpreted as a command name containing =. Bad assignment or comparison?
• Problematic code:
• Correct code:
• Rationale:
• Exceptions:
• Related resources:

This is interpreted as a command name containing =. Bad assignment or comparison?

Problematic code:

"$var"=42
if "$var"=42
then
  true
fi

Correct code:

var=42
if [ "$var" = 42 ]
then
  true
fi

Rationale:

ShellCheck found a command name containing an unquoted equals sign =. This was likely intended as either a comparison or an assignment.

To compare two values, use e.g. [ "$var" = "42" ]

To assign a value, use e.g. var="42"

Exceptions:

None, though you can quote the = to make ShellCheck ignore it: "$var=42".

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.