Skip to content

Conversation

@pranavkm
Copy link
Contributor

@pranavkm pranavkm commented Jul 22, 2020

  • Tweak ILaunchSettingsProvider to return a LaunchSettingsResult
  • Read LaunchSettingsResult during dotnet-run to show message

Based on https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1154478

* Tweak ILaunchSettingsProvider to return a LaunchSettingsResult
* Read LaunchSettingsResult during dotnet-run to show message
@pranavkm pranavkm marked this pull request as ready for review July 22, 2020 01:09
Copy link

@wli3 wli3 left a comment

Choose a reason for hiding this comment

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

My forces is on RunCommand.cs. There are some code lacking coverage. And it is better to have unit tests to cover these code.

targetCommand.EnvironmentVariable("ASPNETCORE_URLS", launchSettings.ApplicationUrl);
}

foreach (var entry in launchSettings.EnvironmentVariables)
Copy link

Choose a reason for hiding this comment

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

no test coverage for this code

return 1;
if (!string.IsNullOrEmpty(launchSettings.ApplicationUrl))
{
targetCommand.EnvironmentVariable("ASPNETCORE_URLS", launchSettings.ApplicationUrl);
Copy link

Choose a reason for hiding this comment

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

no test coverage for this code

@pranavkm
Copy link
Contributor Author

@wli3 I wrote a functional test for the scenarios you listed to make sure previously untested code worked after I basically moved the code around. While I understand it would be great to add unit test coverage for this type, this is not the PR to do it. I'll file an issue to add additional test coverage in this area.

@pranavkm
Copy link
Contributor Author

Filed #12609 as follow up.

@pranavkm pranavkm merged commit 285cac3 into release/5.0.1xx-preview8 Jul 23, 2020
@pranavkm pranavkm added this to the 5.0.1xx milestone Jul 23, 2020
@wli3
Copy link

wli3 commented Jul 23, 2020

While I understand it would be great to add unit test coverage for this type, this is not the PR to do it. I'll file an issue to add additional test coverage in this area.

I don't like this approach. And you dismissed my block directly. Unless it is really hard. Tests should go with the PR.

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.

4 participants