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 SC2102 (markdown)

Vidar Holen
2021-07-25 13:04:46 -07:00
parent b0be87845a
commit b029ddd70a
1 changed files with 2 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
SC2102.md

@@ -37,6 +37,8 @@ cat *.dev.conf *.prod.conf *.test.conf
There is currently a bug in which a range expression whose contents is a variable gets parsed verbatim, e.g. `[$foo]`. In this case, either ignore the warning or make the square brackets part of the variable contents instead. There is currently a bug in which a range expression whose contents is a variable gets parsed verbatim, e.g. `[$foo]`. In this case, either ignore the warning or make the square brackets part of the variable contents instead.
v0.7.2 and below would unintentionally show this warning for subscripts in arrays in `[[ -v array[xx] ]]` and other dereferencing operators. In these versions, you can either [[ignore]] the message or quote the word (as in `[[ -v 'array[xx]' ]]`)
### Related resources: ### Related resources:
* Help by adding links to BashFAQ, StackOverflow, man pages, POSIX, etc! * Help by adding links to BashFAQ, StackOverflow, man pages, POSIX, etc!