Skip to content

Refactor flutter command execution - #5892

Merged
danrubel merged 9 commits into
flutter:masterfrom
danrubel:refactor-flutter-command-execution
Sep 16, 2016
Merged

danrubel merged 9 commits into
flutter:masterfrom
danrubel:refactor-flutter-command-execution

Conversation

@danrubel

Copy link
Copy Markdown

This refactors the FlutterCommand class hierarchy to make it easier to understand and extend.
Fixes #333
@Hixie

@override
Future<int> runInProject() async {
await super.runInProject();
Future<int> runCmd() async {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a style nit: we prefer to use full words in variable name. So, this might be "runCommand"

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sg. Renamed.

@danrubel
danrubel merged commit 1821238 into flutter:master Sep 16, 2016
@Hixie

Hixie commented Sep 16, 2016

Copy link
Copy Markdown
Contributor

LGTM

@danrubel
danrubel deleted the refactor-flutter-command-execution branch September 16, 2016 22:04
@github-actions github-actions Bot locked as resolved and limited conversation to collaborators Aug 15, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

flutter tool "run" vs "runInProject" rationalisation

3 participants