GitHub Package Registry - NuGet - Search API not working correctly

[Falco20019]

Select Topic Area

Bug

Body

According to the specification, the total hits should always include the full amount, independant of take and skip (to allow paging).

On NuGet.org this works fine. TotalHits is always 1145 and changing skip from 0 to 1 will skip the first entry.

On GitHub Packages this does not work at all. TotalHits is always less or equal to take and changing skip from 0 to 1 will do nothing at all. Paging is not possible due to that.

[Falco20019]

According to the GitHub Enterprise support, this is a known bug. There the workaround suggested by them:

• Use the GitHub REST API endpoint /orgs/{org}/packages to retrieve a list of nuget packages for the organization and leverage its pagination capability (using the page and per_page query string parameters)
• Use the GitHub REST API endpoint /orgs/{org}/packages/{package_type}/{package_name}/versions to retrieve a list of versions for each package and leverage its pagination capability (using the page and per_page query string parameters)
• Use the GitHub Packages Nuget Registry API endpoint /{org}/{package_name}/{package_version}.json to retrieve metadata for a package version
  • This allows for retrieval of the .catalogEntry.description attribute which was your requirement that couldn't be met using either the REST API or the GraphQL API.

[Lanrad23]

I've run into the same problem too. It's really annoying when the API doesn't do what it's supposed to, like letting us go through a list page by page with the totalHits, take, and skip settings. This bug makes it hard to look through all the NuGet packages on GitHub Packages because the totalHits doesn't show the real number of packages, and changing the skip setting doesn't actually skip anything like it should.

[Falco20019]

Yep, especially if you use tooling that relies on it to work and does not implement a specific vendor workaround...