Skip to content

Explicitly return undefined from resolveDbgConfig when sessn not started #1548

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.

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

Conversation

rkeithhill
Copy link
Contributor

PR Summary

In the September drop of VSCode this fixes the issue with VSCode
opening launch.json in this case. Technically using return with no expr
works but better to be explicit in this case I think.

microsoft/vscode#54213 (comment)

PR Checklist

Note: Tick the boxes below that apply to this pull request by putting an x between the square brackets.
Please mark anything not applicable to this PR NA.

  • PR has a meaningful title
  • Summarized changes
  • This PR is ready to merge and is not work in progress
    • If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready

In the September drop of VSCode this fixes the issue with VSCode
opening launch.json in this case.  Technically just returning nothing
works but better to be explicit in this case I think.

microsoft/vscode#54213 (comment)
Copy link
Contributor

@rjmholt rjmholt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@rjmholt rjmholt merged commit 7afec44 into PowerShell:master Sep 27, 2018
@rkeithhill
Copy link
Contributor Author

It will be nice in the September drop to not have launch.json pop up every time you attempt to start debugging before the PS session has finished initializing!

@rkeithhill rkeithhill deleted the rkeithhill/return-undefined-resolve-dbg-config branch April 1, 2019 17:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants