Skip to content

Conversation

@danrubel
Copy link
Contributor

Keep the analyze once and continuous analysis implementations separated, but merge the flutter watch back into analyze as flutter analyze --watch.
@Hixie

@Hixie
Copy link
Contributor

Hixie commented Sep 27, 2016

Isn't the plan to go with a "watch" command that does continuous analysis and testing in the background?

@danrubel
Copy link
Contributor Author

danrubel commented Oct 2, 2016

@Hixie
It was, but a majority of the folks I talked with about flutter watch vs flutter analyze --watch thought the later was better.

@Hixie
Copy link
Contributor

Hixie commented Oct 3, 2016

LGTM but @devoncarew would probably be a better reviewer.

});

group('watch', () {
group('analyze --watch', () {
Copy link
Contributor

Choose a reason for hiding this comment

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

No preference, but you could remove this file completely, and move the analyze --watch group into analyze_test.dart.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'd like to keep them separate because the implementations are separate but I just realized I should rename this to analyze_watch_test.dart

@devoncarew
Copy link
Contributor

lgtm

@danrubel danrubel merged commit 9f673ad into flutter:master Oct 4, 2016
yjbanov added a commit to yjbanov/flutter that referenced this pull request Oct 4, 2016
@danrubel danrubel deleted the analyze-watch branch October 4, 2016 18: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.

3 participants