-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
COM.INST.BoolNegation #117
Comments
brigittehuynh
added a commit
that referenced
this issue
Jul 22, 2018
(including case-esac). Tests updated accordingly.
The if [ ! -r "$1" -o ! -f "$1" ] test is correctly analyzed with no false positives with the current version of the rule. |
brigittehuynh
added a commit
that referenced
this issue
Aug 21, 2018
and updated test file accordingly
Merged
Merged
begarco
pushed a commit
to begarco/i-CodeCNES
that referenced
this issue
Jan 25, 2020
…on rule, with localization (including case-esac). Tests updated accordingly.
begarco
pushed a commit
to begarco/i-CodeCNES
that referenced
this issue
Jan 25, 2020
…tside tests) and updated test file accordingly
begarco
pushed a commit
that referenced
this issue
Feb 2, 2020
(including case-esac). Tests updated accordingly.
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Implementation of the rule COM.INST.BoolNegation
Description
Known problems
False positives
Some of them are outside test :
Code example 1 :
debug ${!F}_${!L} "----------------> BEGIN: existsAndNotEmpty $item"
Code example 2 :
debug ${!F}_${!L} $(ls ${reportsDir})
Some others are inside it :
Code :
if [ ! -r "$1" -o ! -f "$1" ]
Function declaration
Description : The checker is not handling some types of functions declaration. The problem is the same one as defined for several rules in #49 .
State of the implementation
The text was updated successfully, but these errors were encountered: