-
Notifications
You must be signed in to change notification settings - Fork 671
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
Improve generation of tasks.json and launch.json assets #590
Conversation
This change allows tasks.json and launch.json to be generated when the workspace root contains a global.json rather than a launch.json. It ensures that appropriate values to the json files to account for the target project being more deeply nested.
|
||
function hasWebServerDependency(targetProjectData: TargetProjectData) { | ||
if (!targetProjectData || !targetProjectData.projectJsonPath) { | ||
return; |
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.
should this be 'return false'? Or does the caller handle undefined?
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.
Good catch. Yes, it should return false.
Otherwise LGTM |
09609e1
to
32d1172
Compare
It is no longer necessary to ensure that the workspace root contains a project.json (or global.json) before offering to generate tasks.json and launch.json. When launched, OmniSharp should scan for projects and, if any or found, we'll offer to generate the assets if needed.
Look better now @gregg-miskelly? |
@DustinCampbell LGTM. Thanks! |
Fixes #556 and #170
This change allows tasks.json and launch.json to be generated when the workspace root contains a global.json rather than a launch.json. It ensures that appropriate values to the json files to account for the target project being more deeply nested.
cc @gregg-miskelly, @rajkumar42, @caslan, @chuckries