Skip to content

Conversation

raquelsa
Copy link
Contributor

…ageId's from install steps.

@@ -22,7 +22,7 @@ public UnpkgProvider(IHostInteraction hostInteraction)

public string Id => IdText;

public string NuGetPackageId => null;
public string NuGetPackageId { get; } = "Microsoft.Web.LibraryManager.Build";
Copy link
Collaborator

Choose a reason for hiding this comment

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

You could've just left the =>, but it doesn't really matter.

Copy link
Contributor

Choose a reason for hiding this comment

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

Why do providers know anything about the NuGet package for restore? This seems like a broken design. Should this be fixed in the command instead?

Copy link
Collaborator

Choose a reason for hiding this comment

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

I think this is good Preview3 as the simplest fix, but in general I completely agree.

Copy link
Contributor

Choose a reason for hiding this comment

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

Can't we just change the packageIds line in RestoreOnBuildCommand.cs to be "Microsoft.Web.LibraryManager.Build"?

Copy link
Contributor

Choose a reason for hiding this comment

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

oh, but currently this allows a provider to specify another package... hm, maybe not then.

Copy link
Contributor

Choose a reason for hiding this comment

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

So, this should be something along the lines of:

  • By default, RestoreOnBuildCommand adds the default package.
  • Providers can specify any other packages they require. Null is allowed, and does not add to the set.

Am I missing something? This still feels like a 5 minute fix and we don't have to track it for another change later.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I would just leave as is for now. Not sure what was the intent of the original design. We can propose design changes later since this fix if for preview3

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Logged issue #155 for the design review

@@ -22,7 +22,7 @@ public UnpkgProvider(IHostInteraction hostInteraction)

public string Id => IdText;

public string NuGetPackageId => null;
public string NuGetPackageId { get; } = "Microsoft.Web.LibraryManager.Build";
Copy link
Contributor

Choose a reason for hiding this comment

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

Why do providers know anything about the NuGet package for restore? This seems like a broken design. Should this be fixed in the command instead?

@raquelsa raquelsa merged commit a339b08 into master Jun 12, 2018
bhsubra pushed a commit that referenced this pull request Jun 13, 2018
@raquelsa raquelsa deleted the dev/raquela/Issue145 branch June 21, 2018 17:53
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