Skip to content
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

[Dotnet Package Search] The search result of the package should be “version” instead of “latestVersion” when executing command “dotnet package search <Package Name> --exact-match --format json” #13158

Closed
v-luzh opened this issue Jan 15, 2024 · 1 comment · Fixed by NuGet/NuGet.Client#5602
Assignees
Labels
Category:BreakingChange Category:Quality Week Issues that should be considered for quality week Found:ManualTests Priority:2 Issues for the current backlog. Type:Bug
Milestone

Comments

@v-luzh
Copy link

v-luzh commented Jan 15, 2024

NuGet Product Used

dotnet.exe

Product Version

.NET SDK 9.0.100-alpha.1.24062.11

Worked before?

It’s not a regression issue since it is a new feature.

Impact

It bothers me. A fix would be nice

Repro Steps & Context

Repro Steps:

1.Patch the latest .NET SDK version (9.0.100-alpha.1.24062.11) with NuGet Client Pipelines - Run 6.9.0.86 artifacts (visualstudio.com).
1.1 Download the Entropy to the desktop of test machine.
1.2 Download and extract the NuGet Client build “6.9.0.86->nupkgs - NonRTM” (named to “nupkgs”) to the desktop of test machine.
1.3 Update the $SDKChannel = "LTS" and $SDKVersion = "9.0.100-alpha.1.24062.11" in the “patchOnWindows.ps1” file of the downloaded “Entropy\SDKPatchTool”.
1.4 Modify the $patchSDKFolder = "C:\Users[UserName]\Desktop\PatchedSDK" and $nupkgsPath = "C:\Users\v-luzh\Desktop\nupkgs" (the path of downloaded nupkgs in step 1.2) in the “patchOnWindows.ps1” file of the downloaded “Entropy\SDKPatchTool”.
2. After patching finished, go to the patchedSDK folder and execute the command .\dotnet package search NUnit --exact-match --format json in powershell.

Expected Results:

The search result of the package should be “version” instead of “latestVersion” since one package only has one latest version. Like the result of the searching the same package with “--format table” by default as below.
image

Actual Results:

The search result of the package shows a lot of “latestVersion” which does not make sense as below screenshot.
image

Note:

Repro rate: 100%

@skofman1
Copy link
Contributor

@Nigusu-Allehu - an additional question regarding the behavior of --exact-match: are we able to show downloads / owners per version? If we don't have the data in the protocol, let's hide it. If we have downloads per version / know the name of the owners, let's display it. Showing null doesn't seem like the best customer experience.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Category:BreakingChange Category:Quality Week Issues that should be considered for quality week Found:ManualTests Priority:2 Issues for the current backlog. Type:Bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants