7x31/shellcheck
1
0
Fork 0
mirror of https://github.com/koalaman/shellcheck.git synced 2025-10-03 19:29:44 +08:00
Code Issues Packages Projects Releases Wiki Activity

Updated SC2155 (markdown)

Vidar Holen
2021-07-25 17:28:44 -07:00
parent 0f153e166d
commit 865736f4cc
1 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
SC2155.md

@@ -19,16 +19,18 @@ In the original code, the return value of `mycmd` is ignored, and `export` will
When first marked for export and assigned separately, the return value of the assignment will be that of `mycmd`. This avoids the problem. When first marked for export and assigned separately, the return value of the assignment will be that of `mycmd`. This avoids the problem.
Note that ShellCheck does not warn about masking of local read-only variables, such as `local -r foo=$(cmd)`, even though this also masks the return value. This is because the alternative `local foo; foo=$(cmd); local -r foo` is repetitive and cumbersome.
#### Exceptions: #### Exceptions:
If you intend to ignore the return value of an assignment, you can either ignore this warning or use If you intend to ignore the return value of an assignment, you can either [[ignore]] this warning or use
```sh ```sh
foo=$(mycmd) || true foo=$(mycmd) || true
export foo export foo
``` ```
Shellcheck does not warn about `export foo=bar` because `bar` is a literal and not a command substitution with an independent return value. It also does not warn about `local -r foo=$(cmd)`, where declaration and assignment must be in the same command. Shellcheck does not warn about `export foo=bar` because `bar` is a literal and not a command substitution with an independent return value.
### Problematic code in the case of `local`: ### Problematic code in the case of `local`: