Disable one_member_abstracts

As already definied in the comment, it makes sense to define interfaces (abstract classes in dart) architecture wise when defining boundaries. A Function reference is not a good replacement because it is very likely that new functions will be added which then would result in a breaking change. Fixes #2
passsy · Oct 4, 2019 · 58007da · 58007da
1 parent 7221732
commit 58007da
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/lib/analysis_options.yaml b/lib/analysis_options.yaml
@@ -347,7 +347,7 @@ linter:
 
     # Defining interfaces (abstract classes), with only one method, makes sense architecture wise
     # https://dart-lang.github.io/linter/lints/one_member_abstracts.html
-    - one_member_abstracts
+    # - one_member_abstracts
 
     # Since Errors aren't intended to be caught (see avoid_catching_errors), throwing anything
     # doesn't cause trouble.