-
Notifications
You must be signed in to change notification settings - Fork 677
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
Improvements to launch.json/tasks.json #2780
Improvements to launch.json/tasks.json #2780
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2780 +/- ##
==========================================
- Coverage 65.13% 64.86% -0.28%
==========================================
Files 104 104
Lines 4506 4505 -1
Branches 654 657 +3
==========================================
- Hits 2935 2922 -13
- Misses 1386 1396 +10
- Partials 185 187 +2
Continue to review full report at Codecov.
|
8c5e86a
to
9fdb94f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice!
This commit contains many improvements to our launch.json and task.json generation. Highlights: - Schema related changes: - Make most of the 'launchBrowser' attributes optional, remove the extra properties from the templates, and improve the schema - In the configuration resolver, add a default value for 'cwd' if we are local debugging - Generator related fixes: - Use a quick pick to allow the user to select which project to launch. Before we would always launch the first one OmniSharp returned. - Remove 'internalConsoleOptions' from the generated templates, and instead default it in the configuration resolver. - Fix several problems with regenerating launch/tasks.json in the case that the file already existed. We had code to delete the files and recreate it, but the logic was wrong leading us to sometimes duplicate content or not create the file at all. - Switch to using the '$tsc' problem matcher. We were using the '$msCompile' matcher, but that assumes that file names will be absolute paths, which isn't what 'dotnet build' provides. - Stop supporting project.json based projects for purposes of generating launch/tasks.json. Continuing to support these now that we let the user pick the startup project was going to be more work than it made sense to support. - In the case of generating launch.json through the configuration provider, we will no longer generate a set of generic configurations in error cases. We will now either use a fall back configuration which is designed to feel like an error, or we will put up an error prompt and return nothing. - Allow generating a tasks.json even if there is no launchable project. Note that we will not automatically generate a tasks.json in this case as I wasn't sure people would really like this, but the 'Generate Assets' command will force it.
9fdb94f
to
9323811
Compare
This commit contains many improvements to our launch.json and task.json generation. Highlights:
Schema related changes:
Generator related fixes:
Testing: Verified open folders/workspaces with the following conditions:
This fixes: #310, #2673 and #2703