Conan search feature: support wildcard only searches

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Work on this issue
• Close this issue

🔥 Problem

In !175392 (comment 2300396080), we noticed that wildcard searches (like '*' or '*/*') are not allowed in the conan search service.

There is a guard that will return an empty array.

It is not clear why we have such restriction. This comment suggests that the conan search feature was built on the requirement of only allowing prefix searches ('prefix*').

🚒 Solution

We could let users input '*' as a search term and let the conan package registry react to it.

The caution to have is that we shouldn't return a 🌊 of results. Thus, we want to implement a limit for result set.

Related to the above, the search feature works at two levels: project and instance. The instance level can create a pretty complex SQL query to get the results. Either the limit restriction can be used to get a proper performance or we can use a smaller limit than the project level or we could allow wildcard search only at the project level.

On top of that, we need a proper order for the results. The generic approach in the package registry is to consider the most recent packages. We could use that as a first

A discussion with product to iron out the UX details is required here.