GitHub Package Registry - NuGet - Search API not working correctly #101961
Replies: 3 comments
-
According to the GitHub Enterprise support, this is a known bug. There the workaround suggested by them:
|
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
-
Yep, especially if you use tooling that relies on it to work and does not implement a specific vendor workaround... |
Beta Was this translation helpful? Give feedback.
-
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 always1145
and changingskip
from0
to1
will skip the first entry.On GitHub Packages this does not work at all.
TotalHits
is always less or equal totake
and changingskip
from0
to1
will do nothing at all. Paging is not possible due to that.Beta Was this translation helpful? Give feedback.
All reactions