You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, we're from the Microsoft.PowerShell.PSResourceGet (previously PowerShellGet) team which is a package manager tool that supports searching, installing and publishing to different repositories with V2 and V3 server protocol support.
We had a user using the V2 endpoint for their repository (https://nuget.cloudsmith.io/repopsresourceget/test/v2) but search fails with our tool because our query uses the $inlinecount=allpages parameter, like so:
https://nuget.cloudsmith.io/repopsresourceget/test/v2/FindPackagesById()?id='Depends'&$inlinecount=allpages&$filter=IsLatestVersion and Id eq 'Depends'
However the response returned from this query shows that the count property is not yet implemented:
Just wanted to ask if there's any plans to implement this? Or would you recommend that users use V3 server protocol endpoint instead? For more context on the issue reported to us, here's the link.
The text was updated successfully, but these errors were encountered:
Hi, we're from the Microsoft.PowerShell.PSResourceGet (previously PowerShellGet) team which is a package manager tool that supports searching, installing and publishing to different repositories with V2 and V3 server protocol support.
We had a user using the V2 endpoint for their repository (https://nuget.cloudsmith.io/repopsresourceget/test/v2) but search fails with our tool because our query uses the
$inlinecount=allpages
parameter, like so:https://nuget.cloudsmith.io/repopsresourceget/test/v2/FindPackagesById()?id='Depends'&$inlinecount=allpages&$filter=IsLatestVersion and Id eq 'Depends'
However the response returned from this query shows that the
count
property is not yet implemented:Just wanted to ask if there's any plans to implement this? Or would you recommend that users use V3 server protocol endpoint instead? For more context on the issue reported to us, here's the link.
The text was updated successfully, but these errors were encountered: