From bf1846e8bba63de3c87f943946a1c39222dfd27f Mon Sep 17 00:00:00 2001 From: Phil Quitslund Date: Wed, 2 Dec 2015 09:09:56 -0800 Subject: [PATCH] Update style guide to recommend `flutter analyze`. --- sky/specs/style-guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sky/specs/style-guide.md b/sky/specs/style-guide.md index 1ae4fa26f4e..51c1ef883b8 100644 --- a/sky/specs/style-guide.md +++ b/sky/specs/style-guide.md @@ -35,7 +35,7 @@ rules, so avoid using that for now.) Always use the Dart Analyzer. Avoid checking in code that increases the output of the analyzer unless you've filed a bug with the Dart -team. (Use "skyanalyzer" to run the analyzer on Flutter code.) +team. (Use `flutter analyze` to run the analyzer on Flutter code.) Use assert()s liberally to describe the contracts that you expect your code to follow.