Giving the way Github API (and Phabricator) has very tight limit for the endpoint we are using (only 30 requests per minute for github), there is a need to implement a sort of caching mechanism so we don't make unnecessary requests to the various platform endpoints trying to re-fetch contributions we have already fetched that day.
The app as it is right now doesn't have this feature. The significance of this is that if two queries are made on the frontend (either from the same person or different people) within a time range of 1 minute, the chances of hitting the API limit (for github expecially) is close to 100% and this is bad UX. The proposed caching feature changes this
Giving the way Github API (and Phabricator) has very tight limit for the endpoint we are using (only 30 requests per minute for github), there is a need to implement a sort of caching mechanism so we don't make unnecessary requests to the various platform endpoints trying to re-fetch contributions we have already fetched that day. The app as it is right now doesn't have this feature. The significance of this is that if two queries are made on the frontend (either from the same person or different people) within a time range of 1 minute, the chances of hitting the API limit (for github expecially) is close to 100% and this is bad UX. The proposed caching feature changes this