You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The current description of the toolArgs is misleading,
Currently, it states:
Arguments to be passed to the Dart or Flutter tool.
These arguments appear after "dart run" or "flutter run": dart (vmAdditionalArgs) run (toolArgs) bin/main.dart (args)
However, this is untrue, when setting the toolArgs with the resident compiler (-r), you get an error from dart stating Could not find an option or flag "-r".
Because it internally runs dart [program] instead of dart run [program]
The current workaround is to add run beforehand to fix this.
To Reproduce
Set toolArgs to ["-r"].
Expected behavior
It should work
Screenshots
Please complete the following information:
You can run the Dart: Collect Diagnostic Information command from the VS Code command palette (F1) to easily capture this information or provide it manually.
Operating System and version: Linux 6.11.11 #1-NixOS SMP PREEMPT_DYNAMIC Thu Dec 5 12:54:34 UTC 2024 - locale is en_GB.UTF-8
VS Code version: 1.98.2
Dart extension version: 3.106.0
Dart/Flutter SDK version: Dart 3.7.1
Target device (if the issue relates to Flutter debugging):
Thanks! I think we had originally used dart run but there was something about it that caused us to stick with just dart. I will update the description to use dart test since the intention was to show the difference between vmAdditionalArgs and toolArgs which is still appropriate there.
Activity
DanTup commentedon Mar 24, 2025
Thanks! I think we had originally used
dart runbut there was something about it that caused us to stick with justdart. I will update the description to usedart testsince the intention was to show the difference betweenvmAdditionalArgsandtoolArgswhich is still appropriate there.Tweak wording of vmAdditionalArgs