Closed jrtechs closed 4 years ago
In reworking the backend API, it should be possible to filter out any data that isn't needed before passing it on to the user.
yep, that's the plan! It should also be possible to make the cache size on the back end a lot smaller
I'm starting to work on this issue in this branch: https://github.com/jrtechs/github-graphs/tree/friends-graph-improvement
Things left to do:
I hope to have this done tomorrow/this weekend.
@jrtechs You might want to use a routing system like the following. That way someone can go to https://github-graphs.com/api/jrtechs
and get the JSON data for user jrtechs
.
router.get("/:username", <your_function>);
@PeterMorganGH that would be ideal. We can make our own restful API of sorts.
We want to better utilize how we are caching things on the backend for the friends of friends graph. The JSON that the GitHub API returns has a ton of URL's that are either redundant or unnecessary for this project. I also want to reduce the number of calls between the front end and the backend GitHub proxy server.