You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here's a snippet or screenshot that shows the problem:
#!/bin/bashecho"${1:missing arg}"
Here's what shellcheck currently says:
No issues detected!
Here's what I wanted or expected to see:
I found a typo where I'd intended to write ${1:?missing arg} but left off the ?. This erroneously turns the expansion into an offset expansion, which (AFAICT) silently ignores non-numeric values.
It would be great if ShellCheck could flag usages of ${var:...} where ... isn't a numeral (or a variable).
The text was updated successfully, but these errors were encountered:
For bugs
shellcheck --version
or 'online'): onlineFor new checks and feature suggestions
Here's a snippet or screenshot that shows the problem:
Here's what shellcheck currently says:
Here's what I wanted or expected to see:
I found a typo where I'd intended to write
${1:?missing arg}
but left off the?
. This erroneously turns the expansion into an offset expansion, which (AFAICT) silently ignores non-numeric values.It would be great if ShellCheck could flag usages of
${var:...}
where...
isn't a numeral (or a variable).The text was updated successfully, but these errors were encountered: