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
Hi, the current Did-you-mean? alternative for SC2006 "Use $(...) notation instead of legacy backticks would be much improved if it removed the would-no-longer-be-necessary backslash quoting that is necessary when using backticks, but is not necessary when using $(...). See the example below.
Here's a snippet or screenshot that shows the problem:
#!/bin/sh
target="`readlink \"$symlink\"`"
Here's what shellcheck currently says:
Line 1296:
target="`readlink \"$symlink\"`"
^-- SC2006 (style): Use $(...) notation instead of legacy backticks `...`.
Did you mean: (apply this, apply all SC2006)
target="$(readlink \"$symlink\")"
Here's what I wanted or expected to see:
Line 1296:
target="`readlink \"$symlink\"`"
^-- SC2006 (style): Use $(...) notation instead of legacy backticks `...`.
Did you mean: (apply this, apply all SC2006)
target="$(readlink "$symlink")"
Note: The difference is the absence of the backslash characters that precede doublequotes in the original. These backslashes would no longer be necessary if backticks were to be replaced with $(...). Making this clear would further encourage making the siggested change.
The text was updated successfully, but these errors were encountered:
Hi, the current Did-you-mean? alternative for SC2006
"Use $(...) notation instead of legacy backticks
would be much improved if it removed the would-no-longer-be-necessary backslash quoting that is necessary when using backticks, but is not necessary when using$(...)
. See the example below.For bugs
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:
Note: The difference is the absence of the backslash characters that precede doublequotes in the original. These backslashes would no longer be necessary if backticks were to be replaced with
$(...)
. Making this clear would further encourage making the siggested change.The text was updated successfully, but these errors were encountered: