Open denis-komarov opened 7 months ago
Thanks @denis-komarov is there a specific package detail that you are missing/need? or are you just looking for 1:1 parity?
@SydneyhSmith thanks, in my case backwards compatibility was broken due to the missing PackageFilename field. It would be great if there was a way to get all the package metadata available through the NuGet V3 API.
Summary of the new feature / enhancement
It says here that "With this module, you no longer need to use PowerShellGet and PackageManagement", but this is impossible, because Find-PSResource returns less NuGet package metadata than Find-Package. Find-PSResource needs an option to control the required level of detail of a package's NuGet metadata so that it can provide the same level of detail that Find-Package currently provides.
Proposed technical implementation details (optional)
Find-PSResource vs. Find-Package - less NuGet package metadata is returned:
The result will be like this:
The result will be like this: