Dmitry Zhifarsky

@g5becks do you have the same problem if you use any Dart version below 3.0?

@FMorschel for multiline comments the rule treats `TODO:` as separate parts of the sentences (which is probably incorrect) and expects an uppercase letter to be the first after the `:`....

The more I look at various examples of todos, the more I'm not sure whether any change should be done here. Most of them start with the uppercase after `:`....

A metric with the automated tests involved, interesting. Thanks!

@DanTup is there a reason why you decided not to proceed with Code Actions? Here is an example on how it looks in analysis_options and is sent from the analysis...

For anyone looking for this rule and willing to try DCM - we have it available https://dcm.dev/docs/rules/common/avoid-redundant-async/, any feedback is welcome!

For anyone looking for a lint rule to handle this: it's now available in DCM https://dcm.dev/docs/rules/common/avoid-shadowing/

@lrhn thank you so much, fixed! The rule currently does not trigger for such cases (at least in the tests). For example, ```dart class TestClass { String value; void someMethod(String...

@DanTup if we can't avoid the weird highlighting thing, I'd personally prefer option 2. But I have a more general question: how will these suggestions work with existing declaration members?...

@pwa-tapptic there are 2 options here: either hide progress indication if the reporter is not a console reporter or add an option of the output file name. Is the progress...