Skip to content

Add facilities to query the association between package versions and package setsΒ #1218

Open
@f-f

Description

@f-f

Right now it's hard to explore the relationship between a package, its versions, and the various package sets - there are only a few facilities:

  • spago ls packages will list the packages present in the package set that the project uses
  • spago registry package-sets will list the package sets that have been published, together with the compiler that they are compatible with

We should improve on that, and have ways to:

  1. list which packages exist in any given package set, not just the local one
  2. list which package sets a certain package version is part of

For each of the points above, I propose that:

  1. we extend spago registry package-sets $SET to show which packages are in the set
  2. we extend spago registry info $PACKAGE with a list of which package set each version is present in.

I'll note that we already have all this info in the Spago DB, and even have code in place to query it, and most likely just needs to be exposed:

spago/src/Spago/Db.purs

Lines 70 to 80 in b5a8ab9

We'll need these when implementing a command for "show me what's in this package set"
selectPackageSetEntriesBySet :: Db -> Version -> Effect (Array PackageSetEntry)
selectPackageSetEntriesBySet db packageSetVersion = do
packageSetEntries <- Uncurried.runEffectFn2 selectPackageSetEntriesBySetImpl db (Version.print packageSetVersion)
pure $ Array.mapMaybe packageSetEntryFromJs packageSetEntries
selectPackageSetEntriesByPackage :: Db -> PackageName -> Version -> Effect (Array PackageSetEntry)
selectPackageSetEntriesByPackage db packageName version = do
packageSetEntries <- Uncurried.runEffectFn3 selectPackageSetEntriesByPackageImpl db (PackageName.print packageName) (Version.print version)
pure $ Array.mapMaybe packageSetEntryFromJs packageSetEntries

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions