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.

Sign up for GitHub

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

Jump to bottom

fix: packages get --recursive runs sequentially #211

Merged
merged 2 commits into from
Oct 18, 2021
Merged

fix: packages get --recursive runs sequentially #211

merged 2 commits into from
Oct 18, 2021

Conversation

felangel
Copy link
Contributor

Description

  • fix: packages get --recursive runs sequentially
    • addresses flutter in use errors
  • feat: improve logging for recursive package installation to report individual package progress

Type of Change

  • ✨ New feature (non-breaking change which adds functionality)
  • 🛠️ Bug fix (non-breaking change which fixes an issue)
  • ❌ Breaking change (fix or feature that would cause existing functionality to change)
  • 🧹 Code refactor
  • ✅ Build configuration change
  • 📝 Documentation
  • 🗑️ Chore

@felangel felangel added bug Something isn't working as expected feature A new feature or request labels Oct 18, 2021
@felangel felangel self-assigned this Oct 18, 2021
marcossevilla
marcossevilla approved these changes Oct 18, 2021
View reviewed changes
lib/src/cli/flutter_cli.dart Show resolved Hide resolved
@felangel felangel merged commit 7ad2196 into main Oct 18, 2021
@felangel felangel deleted the fix/sequential-package-installation branch October 18, 2021 19:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@marcossevilla marcossevilla marcossevilla approved these changes

@jorgecoca jorgecoca Awaiting requested review from jorgecoca

Assignees

@felangel felangel

Labels
bug Something isn't working as expected feature A new feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@felangel @marcossevilla