-
Notifications
You must be signed in to change notification settings - Fork 272
Conversation
@roman-petrov could you please a look too? I'd very happy to get your feedback about this one. |
Codecov Report
@@ Coverage Diff @@
## master #369 +/- ##
==========================================
+ Coverage 79.16% 79.44% +0.27%
==========================================
Files 155 156 +1
Lines 3562 3610 +48
==========================================
+ Hits 2820 2868 +48
Misses 742 742
Continue to review full report at Codecov.
|
lib/src/analyzers/lint_analyzer/rules/rules_list/avoid_returning_widgets/visit_declaration.dart
Outdated
Show resolved
Hide resolved
lib/src/analyzers/lint_analyzer/rules/rules_list/avoid_returning_widgets/visit_declaration.dart
Outdated
Show resolved
Hide resolved
lib/src/analyzers/lint_analyzer/rules/rules_list/avoid_returning_widgets/visit_declaration.dart
Outdated
Show resolved
Hide resolved
@incendial sorry for late response, you mentioned me above but I missed @mention notification in my mail. I will try to improve my email filters to solve this, I am still quite interesting in contributing to this project. This specific update logically looks quite good to me, returning widgets from getters for me looks even worse than returning from functions. |
No problem.
Thanks for taking a look! |
What is the purpose of this pull request? (put an "X" next to an item)
[ ] Documentation update
[ ] Bug fix
[ ] New rule
[X] Changes an existing rule
[ ] Add autofixing to a rule
[ ] Add a CLI option
[ ] Add something to the core
[ ] Other, please explain:
What changes did you make? (Give an overview)
As mentioned here dart-archive/linter#2582 (comment) we should not lint every class method with
Widget
return type, because there are cases where it's totally valid to have aWidget
-returning method and it's used in builders. So this request supports this approach for methods, but still lint getters and global functions as before.