mirror of
https://github.com/SAP/jenkins-library.git
synced 2025-01-30 05:59:39 +02:00
d1e33d6b2f
Is it IMO completly normal to use Boolean.getBoolean(./.).
What is stated in the rule description
| It is often mistakenly used to attempt to read user input or parse
is not a cool reason for having that rule. With such an approach we
can knock out a lot of APIs which can be misunderstood. It is the
duty of the developer to understand the API s?he is using.
The alternate way would be
'Boolean.parseBoolean(System.getProperty('xxx'))'
which is not that convenient like Boolean.getBoolean('xxx').
29 lines
638 B
YAML
29 lines
638 B
YAML
plugins:
|
|
codenarc:
|
|
enabled: true
|
|
checks:
|
|
BooleanGetBoolean:
|
|
enabled: false
|
|
editorconfig:
|
|
enabled: true
|
|
checks:
|
|
# https://github.com/DavidAnson/markdownlint/blob/master/doc/Rules.md#md013---line-length
|
|
MD013:
|
|
enabled: false
|
|
config:
|
|
editorconfig: .editorconfig
|
|
# https://docs.codeclimate.com/docs/advanced-configuration#section-exclude-patterns
|
|
exclude_patterns:
|
|
- "documentation/docs/images/"
|
|
- "cfg/id_rsa.enc"
|
|
fixme:
|
|
enabled: true
|
|
config:
|
|
strings:
|
|
- TODO
|
|
- FIXME
|
|
markdownlint:
|
|
enabled: true
|
|
shellcheck:
|
|
enabled: true
|