9 SC1090

David Auer edited this page 2024-01-26 19:29:57 +01:00

Table of Contents

• Can't follow non-constant source. Use a directive to specify location
• Problematic code
• Correct code
• Rationale
• Exceptions

Can't follow non-constant source. Use a directive to specify location

Problematic code

. "${util_path}"

Correct code

# shellcheck source=src/util.sh
. "${util_path}"

Rationale

ShellCheck is not able to include sourced files from paths that are determined at runtime. The file will not be read, potentially resulting in warnings about unassigned variables and similar.

Use a Directive to point shellcheck to a fixed location it can read instead.

ShellCheck v0.7.2+ will strip a single expansion followed by a slash, e.g. ${var}/util.sh or $(dirname "${BASH_SOURCE[0]}")/util.sh, and treat them as ./util.sh. This allows the use of source-path directives or -P flags to specify the location.

Exceptions

If you don't care that ShellCheck is unable to account for the file, specify # shellcheck source=/dev/null.

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.