farezv / hublogs Goto Github PK

The app is currently limited by GitHub's api call limit

• Decide what data needs to be cached (user profiles for sure)
• Figure out Redis environment variables for heroku deploy
• Add caching calls before api requests
• Add cache store requests after api responses

• Put aggregated repo data under the list of dev profiles
• Add menu links on results page jumping between sections
• Show commit data
• Show PR data
• Show issue data

First step to figuring out which repos are active

If I only cache individual member data but don't cache member lists, and I've hit my api limit, I can't find the list of members that belong to the organization.

For instance, memberA and memberB belong to orgZ and those 2 members have been cached. If my api limit is reached, and someone searches for orgZ I have no way of knowing if memberA or memberB belong to orgZ. Therefore, I need to cache orgZ member list

Probably best to create a list of repo objects under hubuser class. Each repo class can have appropriate stats

Figure out how to delay loading the page until all profiles have been acquired either from cache or an api call.