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
{{ message }}
This repository has been archived by the owner on May 26, 2023. It is now read-only.
We could also go all in ESLint style and have a few different types of statements, such as ' bslint-disable, ' bslint-enable, ' bslint-disable-next-line, ' bslint-disable-line.
A new proposal that surfaced recently was to use conditional compilation constants as annotations for scoped blocks. For example
#const__suppress_wist_rule_name=truefunction breakRuleHere() asVoid
...
end function#const__suppress_wist_rule_name=truefunction anotherFunction() asVoid
...
end function
It could also be possible use them as fenced blocks to enable and disable rules.
#const__suppress_wist_rule_name=falsefunction breakRuleHere() asVoid
...
end function#const__suppress_wist_rule_name=true
Something like a comment-based format to override rules.
Maybe
' bslint "rule-name": "severity"
As an example to turn off the rule
no-print
you would add the following comment:' bslint "no-print": "off"
The text was updated successfully, but these errors were encountered: