Skip to content

Use 'resolveDebugConfigWithSubVariables' - #6328

Merged
Andrew Wang (WardenGnaw) merged 2 commits into
masterfrom
dev/waan/waitForPrelaunchTask
Oct 15, 2020
Merged

Andrew Wang (WardenGnaw) merged 2 commits into
masterfrom
dev/waan/waitForPrelaunchTask

Conversation

@WardenGnaw

Copy link
Copy Markdown
Member

This PR uses the
DebugConfigurationProvider.resolveDebugConfigurationWithSubstitutedVariables
which allows the debug configuration to wait for the preLaunchTask to
complete before continuing on and resolving environment variables or processes
that may have been set in the 'tasks.json'.

This also resolves the logging issue where the 'Build and Debug Active
File' preLaunchTask uses the current file but we switch to the output
window for logging.

Undo: #6304 but VS Code bug is still valid.

Related Issues: #5287

This PR uses the
DebugConfigurationProvider.resolveDebugConfigurationWithSubstitutedVariables
which allows the debug configuration to wait for the preLaunchTask to
complete before continuing on and resolving variables that may have been
set in the 'tasks.json'.

This also resolves the logging issue where the 'Build and Debug Active
File' preLaunchTask uses the current file but we switch to the output
window for logging.
@WardenGnaw
Andrew Wang (WardenGnaw) merged commit 2ec525e into master Oct 15, 2020
@sean-mcmanus

Copy link
Copy Markdown
Contributor

Andrew Wang (@WardenGnaw) I think this broke Linux/Mac debugging with F5 (Build and Debug Active File).

Sean McManus (sean-mcmanus) added a commit that referenced this pull request Oct 16, 2020
@bobbrow
Bob Brown (bobbrow) deleted the dev/waan/waitForPrelaunchTask branch January 5, 2021 17:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

debugger enhancement Improvement to an existing feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants