feat: Improve search

[1a35e1]

Howdy so I had a quick dive on the Gitcoin APIs they seem to have all the necessary endpoints to facilitate the discussion that was originally started here: https://t.me/c/1724749443/1/10504

One tool that is super helpful exploring GraphQL APIs is https://graphql-kit.com/graphql-voyager/

• Copy the content from
  intospection.json
• Paste the results of the introspection Change Schema -> Introspection -> Display

From here it seems:

• For the project search query searchProjects(searchTerm: $searchTerm) seems to do the job we want.
• We can minimise the number of calls and remove unnecessary filters, leaning on the API itself.
• From this I added a ProjectContext so data is fetched only once in a requests lifecycle
• We can lean on other apis such as query donations() to paginate data

TODO

• Reimplement DonationsTable
• rounds subpages
• Autocomplete jank
• Reimplement generateMetadata

[sonarqubecloud]

Quality Gate passed

Issues
10 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[duckdegen]

Hey @johnshift can you provide an estimate on when this will be merged, and if additional steps are necesssary?

[johnshift]

Heya @1a35e1 @duckdegen. I’m tied up with other tasks at the moment but will take a look soon!

[johnshift]

Hey @1a35e1, sorry for the delayed reply. Holidays kept things busy. Hope you had a great break!
Thanks for diving into the Gitcoin APIs. We really appreciate the effort! 🙌

It looks like the implementation revolves around the searchProjects(searchTerm: $searchTerm) query.
Just to share some context, we’re currently filtering projects by their application status to include only those with a status of "approved," which doesn’t seem to be supported here.

If you have ideas for adjusting the approach or leveraging another API endpoint to better align with this requirement, we’d love to hear them.

[MasterHW]

Just to share some context, we’re currently filtering projects by their application status to include only those with a status of "approved," which doesn’t seem to be supported here.

hi John, correct there is no elegant way to filter application status on a project model query. this is a limitation because not all projects even have applications, so filtering on a field that may or may not exist is harder for us to structure.

a less elegant approach that may still work for you is to return the applications { status } field, and decide whether to display this on the page or not by whether it has an APPROVED application.

let me know if this is satisfactory or not.