Skip to content

Conversation

@DanTup
Copy link
Member

@DanTup DanTup commented Apr 29, 2019

Previously we could simultaneously fire off many, but pub doesn't handle concurrent fetches very well. This will run it automatically for one change, but show the "Some packages are out of date" prompt for > 1.

Fixes #1651.

Previously we could simultaneously fire off many, but pub doesn't handle concurrent fetches very well. This will run it automatically for one change, but show the "Some packages are out of date" prompt for > 1.

Fixes #1651.
@DanTup DanTup added is enhancement in editor Relates to code editing or language features in commands Relates to commands (usually invoked from the command Palette) labels Apr 29, 2019
@DanTup DanTup added this to the v2.26.1 milestone Apr 29, 2019
@DanTup DanTup merged commit a2f53e8 into master Apr 29, 2019
@DanTup DanTup deleted the batch-pub-get-on-pubspec-changes branch April 29, 2019 14:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

in commands Relates to commands (usually invoked from the command Palette) in editor Relates to code editing or language features is enhancement

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Running "pub get" on pubspec.yaml changes during a Git branch change is too agressive

2 participants