NuGet/Home

[Feature]: Make dotnet list package work without restore when using lock files

Open

#11,770 建立於 2022年4月22日

在 GitHub 查看
 (9 留言) (1 反應) (0 負責人)HTML (1,459 star) (292 fork)batch import
Area:RestoreRepeatableBuildFunctionality:ListPackagePriority:3Product:dotnet.exeType:Featurehelp wanted

描述

NuGet Product(s) Involved

dotnet.exe

The Elevator Pitch

(Was asked to post this here instead of https://github.com/dotnet/sdk/issues/24194)

We are running dotnet list package (with --vulnerable, --outdated, and --deprecated) in a CI pipeline. This seems to require restoring the projects first. This adds overhead in the pipeline, which seems unnecessary since we use lock files (packages.lock.json) which AFAIK contains all necessary information. I propose allowing dotnet list package to work with the information in lock files, without needing a restore.

Additional Context and Details

No response

貢獻者指南

技術棧
csharp
領域
cli
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
4
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
over 1 week
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
C# developmentNuGet client internalsUnderstanding of lock files
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
35
研究方向
Investigate the dotnet list package command implementation in the dotnet/sdk repository. Understand how the command currently triggers a restore and where to intercept to use lock file data. Look at the NuGet lock file format (packages.lock.json) to determine if it contains all needed information. Review the linked issue dotnet/sdk#24194 for context. Consider creating a prototype that bypasses restore when lock files are present.