Skip to content

Show compound licenses in the front-end#1228

Open
KiaraGrouwstra wants to merge 2 commits intomainfrom
compound-licenses
Open

Show compound licenses in the front-end#1228
KiaraGrouwstra wants to merge 2 commits intomainfrom
compound-licenses

Conversation

@KiaraGrouwstra
Copy link
Copy Markdown
Collaborator

@KiaraGrouwstra KiaraGrouwstra commented Apr 25, 2026

Builds upon the back-end change (#1227) to show compound licenses in the front-end.

How this looks in action:

image

Note that traditional license lists are shown as before to distinguish when we have vs lack such data -- we do expect explicit migration of licenses to ensure semantics are reflected as intended.

Disclaimer: i used a coding agent in the creation of this patch.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Apr 25, 2026

@github-actions github-actions Bot temporarily deployed to pull request April 25, 2026 12:07 Inactive
Nixpkgs is introducing compound license expressions (AND, OR, WITH,
PLUS) via NixOS/nixpkgs#468378.  This extends the `License` enum to
deserialize the new `licenseType`-tagged structures, recursively
flattens them into leaf licenses for the search index, and exposes a
`package_license_expression` field carrying the SPDX-style expression
string when compound licenses are present.

Bump import index version to 47 for the new field.
When the backend provides a `package_license_expression` (SPDX-style
string for compound licenses), display it as the license label instead
of the flat list of individual licenses.  For packages with only simple
licenses the behavior is unchanged.

Bump frontend index version to 47 to match the new schema.
@github-actions github-actions Bot temporarily deployed to pull request April 25, 2026 13:56 Inactive
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant