Point 1 can easily be fixed, but point 2 creates much more of a problem. The only viable workaround would be to retrieve every package and then filter locally. Would this work in your case? I don't know whether the search API also flows through to an upstream source. If so, this would definitely not be a solution.
Thank you for your reply, Joe. LINQPad is a great product.
If space can be removed, one can rename their package and put 'LINQPadDriver' (case insensitive) in package name and this package will be returned by DevOps feed. That was my personal plan. Looks like they do not search by tag values, nor do they search by description. Another alternative will be to publish the package in a different NuGet feed implementation (e.g. nuget.org), but that is not currently possible. Azure DevOps Authentication works fine though.
If upstream sources are used, DevOps passes query to them and they DO support searching by tags or/and trim the space at the end.
Comments
Point 1 can easily be fixed, but point 2 creates much more of a problem. The only viable workaround would be to retrieve every package and then filter locally. Would this work in your case? I don't know whether the search API also flows through to an upstream source. If so, this would definitely not be a solution.
Thank you for your reply, Joe. LINQPad is a great product.
If space can be removed, one can rename their package and put 'LINQPadDriver' (case insensitive) in package name and this package will be returned by DevOps feed. That was my personal plan. Looks like they do not search by tag values, nor do they search by description. Another alternative will be to publish the package in a different NuGet feed implementation (e.g. nuget.org), but that is not currently possible. Azure DevOps Authentication works fine though.
If upstream sources are used, DevOps passes query to them and they DO support searching by tags or/and trim the space at the end.