From d1e33d6b2fb16f083822015045505c8d3e59c3e5 Mon Sep 17 00:00:00 2001
From: Marcus Holl <marcus.holl@sap.com>
Date: Thu, 8 Nov 2018 13:40:13 +0100
Subject: [PATCH] Disable check for Boolean.getBoolean()

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').
---
 .codeclimate.yml | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/.codeclimate.yml b/.codeclimate.yml
index 9b68739e4..f16213b9a 100644
--- a/.codeclimate.yml
+++ b/.codeclimate.yml
@@ -1,6 +1,9 @@
 plugins:
   codenarc:
     enabled: true
+    checks:
+      BooleanGetBoolean:
+        enabled: false
   editorconfig:
     enabled: true
     checks: