-
Notifications
You must be signed in to change notification settings - Fork 253
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
installing package from a local source that doesn't exist throws a bogus message #1674
Comments
@rohit21agrawal @yishaigalatzer @harikmenon @rrelyea Please let me know if this looks fine? Case 1 - invalid local path
Case 2 - Invalid http path that does not contain the package
Case 3 - Random String as path
|
a random string can be the name of a source in the nuget.config file |
Yes. As we discussed offline, I will be removing the check for that. Thanks! |
@yishaigalatzer @harikmenon @rrelyea Please let me know if this looks fine? I have edited them, based on feedback from @rohit21agrawal . Case 1 - invalid local path PM> install-package Rules -source c:\temp\data
Case 2 - Valid http path that does not contain the package
Case 3 - Random String as path
Case 4 - Known source
|
Case 2 seems confusing. Why do we talk about package metadata? |
When the implementation PR is pushed we need to add end-to-end tests for each of the cases. |
@harikmenon : Realized that we cant have different error message for a random string, since its treated as a local relative string ( like a local folder name!). So the case 3 would be updated to the following - Update Case 3 -
Let me know your thoughts or if this is fine? |
Sounds good to me. |
@harikmenon : Had an offline talk with @rrelyea about the complexity of the error message in Case 2. I will update that to the following, simpler error message - Update Case 2 -
Let me know if this looks fine? |
Original issue commits : NuGet/NuGet.Client@0f83bee NuGet/NuGet.Client@779f2bb Improved Case 2 error message commit : NuGet/NuGet.Client@370687d End to End test cases commit : NuGet/NuGet.Client@018ebd6 |
Run the following command from Power Shell, of course make sure the folder
c:\temp\data
does not exist on your machineThe error says
Unable to find package 'Rules'
instead of cannot find the folder (or a mix of the two)The text was updated successfully, but these errors were encountered: