CAS-541: Search Endpoint

[jbluks]

• Fix the endpoint to be /search?text=search+text to allow for spaces. If text is blank, the default search for featured communities will be performed
• Bugs in the filter counts also fixed.

[linear]

CAS-541

[germanurrus]

Looking good! Thanks for the tweaks in the frontend! Made some comments

[germanurrus]

It looks like the count url param is not taken into account on the search result, I've created a set for testing and results array has more elements than the count number on the first pull from the backend (FE sends 10 and backend returns all results):

The other thing I noticed is that results are not filtered with the text search after the space, in this case "before 2" should return only the community that has "before 2" but it returns the same as if I would enter "before" (The name of the community makes no sense :( ). May it has to do with the configuration of the search plug-in?

[jbluks]

Fixed the search results count/start. Was missing from the search text query. The results are inclusive of any of the words, so because the search contains "before" it will return any community with that word, even though the search contains another search string. The search does not "narrow" with new terms. I think this makes sense for a browser page.

[germanurrus]

there's one last glitch while filtering, if the frontend sends the filter results should be narrowed but the filter should return the same amount originally created for the text search:

Screen.Recording.2022-10-06.at.16.33.26.mov

[germanurrus]

on line 70:

 getNextPageParam: (lastPage) => {
          // custom adjustment
          const { next, start, count, totalRecords } = lastPage?.results ?? {};
          return [start + count, count, totalRecords, next];
        },

[germanurrus]

Tested locally and works as expected!