You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Usage: flutter analyze [arguments]
-h, --help Print this usage information.
--[no-]flutter-repo Include all the examples and tests from the Flutter repository.
--[no-]current-directory Include all the Dart files in the current directory, if any.
(defaults to on)
--[no-]current-package Include the lib/main.dart file from the current directory, if any.
(defaults to on)
--[no-]dartdocs List every public member that is lacking documentation (only examines files in the Flutter repository).
--[no-]preamble Display the number of files that will be analyzed.
(defaults to on)
--[no-]congratulate Show output even when there are no errors, warnings, hints, or lints.
(defaults to on)
--watch Run analysis continuously, watching the filesystem for changes.
--[no-]pub Whether to run "pub get" before executing this command.
(defaults to on)
I wonder if we could eliminate some of these options entirely, and simplify the matrix of possibilities a bit?
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
devoncarew commentedon Jun 6, 2016
I wonder if we could eliminate some of these options entirely, and simplify the matrix of possibilities a bit?
pq commentedon Jun 6, 2016
Maybe this can be removed given that we should get the equivalent like so:
flutter analyze .(Bonus points for being shorter than
flutter analyze --current-directory😄 )Hixie commentedon Jan 30, 2017
Closing in favour of #7274
Revert "Move texture registry ownership to platform view (flutter#4348)…
github-actions commentedon Sep 5, 2021
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.