[NuGet.org Bug]: License expressions aren't displayed correctly

[iTrooz]

Impact

It bothers me. A fix would be nice

Describe the bug

On the package view page, Licence expressions aren't displayed correctly. For example my project is using the expression <PackageLicenseExpression>LGPL-2.1-only OR LGPL-3.0-or-later</PackageLicenseExpression> but it is rendered as:

(link)

Repro Steps

• Create a project
• Use a license expression with a OR, such as <PackageLicenseExpression>LGPL-2.1-only OR LGPL-3.0-or-later</PackageLicenseExpression>
• Pack using dotnet pack FreeDesktopSecrets.csproj --configuration Release
• Upload to NuGet (notice the preview renders properly)
• The package page doesn't render correctly

Expected Behavior

It should read LGPL-2.1-only license OR LGPL-3.0-or-later license instead

Screenshots

No response

Additional Context and logs

No response

[fjssilva]

License exceptions, specified by using the "WITH" operator, are affected by the same. I have <PackageLicenseExpression>GPL-2.0-only WITH Universal-FOSS-exception-1.0</PackageLicenseExpression> in the project, which renders as:

Seen in https://www.nuget.org/packages/MySql.Data.

[JPGrieb]

Should GPL-3.0-or-later license WITH Autoconf-exception-2.0 license be displayed with or without the word 'license' on the end?

[fjssilva]

I'd say without any of them, or with only the last one but not as part of the link, even if single license.

[JPGrieb]

I'll fix this issue.

[kzu]

Another example: https://www.nuget.org/packages/Devlooped.WhatsApp

[joelverhagen]

This is deployed to DEV and resolved. Thanks to @JPGrieb for taking care of this!