Feature: Implement voting logic for repos

[bdougie]

Type of feature

Feature

Current behavior

Today the api is listing repos based on relevancy in open sauced.

• api.opensauced.pizza
• The above is powered by a private DB hosted on supabase

Desired solution

We need a global state that can store votes from users

• Add local state to fetch vote data
• Implement vote column in supabase db
• Alternatively we could use a public JSON file to store votes as an intermediary.

Additional context

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[0-vortex]

IMHO anything calling a specific microservice or API endpoint could use some local mocking or container composing. How do you feel about doing some compatibility upgrades in https://github.com/open-sauced/hot-sauce-api ?

[bdougie]

Hey, @0-vortex interested in hearing more about this microservice. I think I will try to figure out the voting logic this week. I am thinking about creating a table in the supabase DB with votes captured. I am also thinking this will be blocked slightly by #20, since I will need to store the votes based on the logged-in user.

Also, side note: I am going to look into making the data public via the new supabase studio.

[bdougie]

Going to be starting work on this. The current plan

• Create table that stores votes from users: githubUserIds, and vote timestamps
• Write votes to the recommendations table
• Mock GitHub login until Need Open Sauced GitHub Login #20
• Connect supabase client to write to DB directly
• Implement local state storage.
• Implement API automation for updates.
• Create a supabase studio environment so all the above is viewable and approachable to others.

The scope may be quick, but I will open issues if things start taking too long.

[hokagedemehin]

You can also consider using React Context API for global state management. That way you can have a save a vote and have it available across the app for other components to use.

Redux can also do the same but I think the set up might be a lot

[github-actions]

🎉 This issue has been resolved in version 1.6.0 🎉

The release is available on:

• GitHub release
• ghcr.io container (@latest dist-tag)

Your semantic-release bot 📦🚀