Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't require .packages file for flutter packages command #12258

Merged
merged 1 commit into from
Sep 26, 2017
Merged

Don't require .packages file for flutter packages command #12258

merged 1 commit into from
Sep 26, 2017

Conversation

tvolkert
Copy link
Contributor

(it's the command that populates the .packages file)

(it's the command that populates the .packages file)
@tvolkert
Copy link
Contributor Author

Tests to follow, but sending this out to unblock broken builds on other repos.

Copy link
Contributor

@yjbanov yjbanov left a comment

Choose a reason for hiding this comment

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

LGTM

@tvolkert tvolkert merged commit bb0a724 into flutter:master Sep 26, 2017
@tvolkert tvolkert deleted the fix branch September 26, 2017 16:12
@mit-mit
Copy link
Member

mit-mit commented Sep 26, 2017

Thanks!

@@ -347,7 +347,7 @@ abstract class FlutterCommand extends Command<Null> {
}

// Validate the current package map only if we will not be running "pub get" later.
if (!(_usesPubOption && argResults['pub'])) {
if (parent?.name != 'packages' && !(_usesPubOption && argResults['pub'])) {
Copy link
Contributor

Choose a reason for hiding this comment

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

test?

@tvolkert
Copy link
Contributor Author

test?

See comment above. Writing tests as we speak, but I wanted to unbreak the build first.

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.

5 participants