Don't default package description to "Package Description". · NuGet/Home#8966

(10 comments) (3 reactions) (0 assignees)HTML (1,459 stars) (292 forks)batch import

Area:PackageDefinitionFunctionality:PackIcebox cleanup candidatePriority:3Status:InactiveType:Bughelp wanted

説明

If I create a new class library project (sdk-style) and "pack" it, it produces a package with a description of "Package Description". I can override this by providing a <Description> property in my csproj (such an override cannot be empty). If it is a required field in the package, make it a build error (with an explanation of how to define it) if it isn't defined rather than defaulting it to a useless value.

If you don't think this is a problem, then I would counter with: https://www.nuget.org/packages?q=%22Package+Description%22 21,031 results

Even a lot of Microsoft's own packages have this default description. Honestly, it's a bit embarrassing.

コントリビューターガイド

技術スタック: csharp
領域: build systemdeveloper experience
Issue 種別: feature
難度: 2
推定時間: 1-3 hours
活動状況: stale
明確さ: clear
前提条件: Basic understanding of NuGet packagingFamiliarity with .NET project files
初心者向け度: 60
調査方針: The issue suggests making the package description required by throwing a build error if not defined instead of defaulting to 'Package Description'. To implement this, one would need to locate where the default description is set in the NuGet client code, likely in the packaging task or in the build logic. Look in the NuGet.Client repository for the code that generates the nuspec or package metadata. The change would involve either removing the default or adding a check to error if the Description property is not explicitly set in the project file. There are no linked PRs or assignees, so this issue is available for contribution.