Search is not possible in Python Details page

[carlosthe19916]

Currently the user loses the posibility of continue searching for packages once he enters to the Package Details Page. The image below is the Package Details page where the only way of keep searching for more packages is to click on "Back to packages" button which forces to select a distribution once again.

There are also some images of different language package search engines. Notice that all those search engines do not block the user to keep searching for additional packages using the input text at the top of the package. Shouldn't we offer something similar too? Seems like this pattern is a well know and accepted practice.

cc: @CryptoRodeo
this issue is to first discuss and make a conscious decision given the fact that we don;t have much time and postponing things is also an alternative

[CryptoRodeo]

Hmm... if the user were to search from the details page, then those search results should be restricted to the same distribution that the current package they're viewing comes from, right?

[carlosthe19916]

Hmm... if the user were to search from the details page, then those search results should be restricted to the same distribution that the current package they're viewing comes from, right?

yep, at least that would be the idea.

[CryptoRodeo]

Just brainstorming here: if the list of packages for a specific distribution are stored in the Tanstack query cache, then maybe we can reuse that same data for the search bar? Something like this:

1. Call useFetchUniquePackages(distributionBasePath) directly in PythonDetails (or a new search component on that page).
2. Use something like a Search with auto complete for the search bar and results where each result is a link to a package details page: https://www.patternfly.org/components/search-input/react-demos#search-with-autocomplete
   -> I can't think of a better component at this time but if you know any then we can use that.

I think useFetchUniquePackages only returns package names though, right? So if we wanted to display more data than just the name this becomes more complex.

If we start with just reusing the package list data I think it'll be a great feature to add.

[CryptoRodeo]

Here's a demo of that idea:

search-bar.mp4

We can discuss how this should look with UX, but the overall idea of reusing the data from useFetchUniquePackages is here. You can see the code in #26

[carlosthe19916]

Looks great, I think it would be a good addition