5 SC2153

Bruce Ricard edited this page 2023-07-07 12:59:05 -04:00

Table of Contents

• Possible Misspelling: MYVARIABLE may not be assigned. Did you mean MY_VARIABLE?
• Problematic code:
• Correct code:
• Rationale:
• Exceptions:

Possible Misspelling: MYVARIABLE may not be assigned. Did you mean MY_VARIABLE?

Problematic code:

MY_VARIABLE="hello world"
echo "$MYVARIABLE"

Correct code:

MY_VARIABLE="hello world"
echo "$MY_VARIABLE"

Rationale:

ShellCheck has noticed that you reference a variable that is not assigned in the script, but which has a name similar to another known variable. You should verify that the variable name is spelled correctly.

Note: This error only triggers for environment variables (all uppercase variables), and only when they have names similar to another known variable in the script. If the variable is script-local, it should by convention have a lowercase name, and will in that case be caught by [SC2154] whether or not it resembles another name.

Exceptions:

If you've double checked and ensured that you did not intend to reference the specified variable, you can disable this message with a directive. The message will also not appear for guarded references like ${ENVVAR:-default} or ${ENVVAR:?Unset error message here}.

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.