SC2163 screams when using variables... to export variable names dynamically.
SC2163's description admits that it merely slightly improves the wording of error messages; that export already correctly handles situations where the outer variable name is not set.
SC2163 ignores the presence of set -[ef]u[o pipefail] by the top of the script.
SC2163 insists on ${var?} interpolation syntax to reference variables. But only for export, not the legions of other variable uses where they could just as well be unset.
Sure, blare sirens every time liquid is inserted into the gas tank on under full moons on Tuesdays, just in case the liquid wasn't fuel.
I'm disabling SC2163 in my configurations. Recommend removing this rule from future releases.
SC2163 screams when using variables... to export variable names dynamically.
SC2163's description admits that it merely slightly improves the wording of error messages; that
exportalready correctly handles situations where the outer variable name is not set.SC2163 ignores the presence of
set -[ef]u[o pipefail]by the top of the script.SC2163 insists on
${var?}interpolation syntax to reference variables. But only for export, not the legions of other variable uses where they could just as well be unset.Sure, blare sirens every time liquid is inserted into the gas tank on under full moons on Tuesdays, just in case the liquid wasn't fuel.
I'm disabling SC2163 in my configurations. Recommend removing this rule from future releases.