From 5975bd1f1e4dd522b83d6c365696da694c114a7c Mon Sep 17 00:00:00 2001
From: Tim Jaacks <tim.jaacks@seco.com>
Date: Mon, 31 Jul 2023 10:19:58 +0200
Subject: [PATCH] Sourcery: keep remove-zero-from-range check disabled

IMO explicit declaration of lower and upper limits makes code easier to
read than using an implicit default value.

See for reference:
https://docs.sourcery.ai/Reference/Python/Default-Rules/remove-zero-from-range/
---
 scripts/.sourcery.yaml | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/scripts/.sourcery.yaml b/scripts/.sourcery.yaml
index 328f19b5..1b0d5913 100644
--- a/scripts/.sourcery.yaml
+++ b/scripts/.sourcery.yaml
@@ -8,6 +8,8 @@ rule_settings:
   disable:
   # Code is easier to read without this
   - min-max-identity
+  # Keep explicit lower range limit instead of using implicit default value
+  - remove-zero-from-range
   # FIXME: verify if we want to keep the checks below.
   # If not, remove them. If yes, move them above this comment.
   - use-fstring-for-formatting
@@ -28,7 +30,6 @@ rule_settings:
   - de-morgan
   - merge-nested-ifs
   - remove-dict-keys
-  - remove-zero-from-range
   - use-named-expression
   - use-next
 
-- 
GitLab