flutter analyze takes --write=path/report-name.txt option argument. Reports generated in this way are slightly different than the flutter analyze, making flutter_lint unable to parse the results:

$ flutter analyze --no-fatal-infos --no-fatal-warnings > flutter_analyze_report.txt
1 issue found. (ran in 12.0s)
$ cat flutter_analyze_report.txt
Analyzing rtyst_flutter...                                      
   info • Sort constructor declarations before other members • lib/main.dart:23:3 • sort_constructors_first

$ flutter analyze --no-fatal-infos --no-fatal-warnings --write=flutter_analyze_report.txt
Analyzing rtyst_flutter...                                      
   info • Sort constructor declarations before other members • lib/main.dart:23:3 • sort_constructors_first
1 issue found. (ran in 13.2s)
$ cat flutter_analyze_report.txt
[info] Sort constructor declarations before other members (/builds/rtyst/rtyst_flutter/lib/main.dart:23:3)

Because --write is the supported way for flutter to generate reports, flutter_lint should work with it.

Would it be possible to also report formatting issues by calling dartfmt/flutter format? I currently have an action that calls the following:

find . -name *.dart -not -path "./lib/generated/*" -exec flutter format --set-exit-if-changed --dry-run {} +

and fails if it finds any formatting issues, but it would be amazing if they could be reported like the flutter analyze output. It doesn't need to report specific issues, even just "Formatting issues found" as a warning on the filename would be great.

First, thanks for this, I would be cool to have an option to run it only over modified files

Current

There's an option to run only on modified files only_modified_files,

Expected

Be able to run only over modified files, too.