Add some logging to indicate why "pub get"/"pub upgrade" may be required #4474

Activity

1. DanTup

   added

   is enhancementAn enhancement or improvement that should be listed in release notes but is not a bug fix.An enhancement or improvement that should be listed in release notes but is not a bug fix.

   in commandsRelates to commands (usually invoked from the command Palette)Relates to commands (usually invoked from the command Palette)

   on Mar 30, 2023
2. DanTup

   added this to the v3.62.0 milestone on Mar 30, 2023
3. DanTup

   changed the title [-]Add some logging to indicate why "pub get" may be required[/-] [+]Add some logging to indicate why "pub get"/"pub upgrade" may be required[/+] on Mar 30, 2023
4. DanTup commented on Mar 30, 2023

   

   DanTup

   on Mar 30, 2023

   MemberAuthor

   More actions

   @jacob314 @kenzieschmoll I've added some logging so when you see this prompt, if you open the extension log (Dart: Open Extension Log from the command palette (F1)), it'll include messages like this:

   [16:20:44] [General] [Info] Found 1 folders requiring "pub get" or "pub upgrade":
       /Users/danny/Desktop/dart_sample (get: true, upgrade: false, reason: package_config.json is missing)
   

   [16:21:36] [General] [Info] Found 1 folders requiring "pub get" or "pub upgrade":
       /Users/danny/Desktop/dart_sample (get: true, upgrade: false, reason: pubspec.yaml was modified (Thu Mar 30 2023 16:21:35 GMT+0100 (British Summer Time))
           more recently than pubspec.lock (Thu Mar 30 2023 16:21:10 GMT+0100 (British Summer Time)))
   

   I'm interested to know what happens in the cases where you see this and don't think you should. Our check is fairly basic, so changing git branch will prompt to run if the checkout have modified the pubspec, but it shouldn't if it didn't.

   (I'm planning to push a new pre-release version of the extension shortly, so if you're on the pre-release version you may already have the change by the time you read this.. it'll be version v3.61.20230330 - you may need to "reload" for it to activate).
5. DanTup

   closed this as completedin 385681bon Mar 30, 2023
6. keertip

   added a commit that references this issue on Sep 2, 2025

   Improve logging of reasons why "pub get" may be required

   ...

   385681b