bermarte/bermarte.github.io

my GitHub-homepage

bermarte.github.io's Issues

caching-experiment

From Shaun

So, the idea is, when you don't expect data for an external service to change often, you store a copy of it on your own service. This has two big benefits:

1. You're not hitting any sort of rate limits on the external service
2. Your data retrieval is much much faster

refactoring

From HackYourFutureBelgium/class-11-12#290 (Bram)

• Your Repo class currently handles the loading of all the repositories that you want. A class should be as small as possible, in this case a single repository.
• Nice job on already using async/await syntax for this project.
• Your data fetching code is currently modifying the global repos variable. This will have the side-effect that if you ever call repo.getRepos a second or third time you'll have the same repositories included twice.
• On your projects section you're filtering the list of projects to a certain selection. But what would happen if you started creating more repositories and the ones you want to display are no longer returned because GitHub's API paginates the list of repositories? Since you already know the names of the repositories you want to include you could also use this endpoint to retrieve them individually. This is also a good way to experiment a bit with concurrent requests using Promise.all

refactoring

Bram -refactoring

HackYourFutureBelgium/class-11-12#290 (comment)

Really nice job with the portfolio. It looks really modern and I like the small animations!

• Your Repo class currently handles the loading of all the repositories that you want. A class should be as small as possible, in this case a single repository.
• Nice job on already using async/await syntax for this project.
• Your data fetching code is currently modifying the global repos variable. This will have the side-effect that if you ever call repo.getRepos a second or third time you'll have the same repositories included twice.
• On your projects section you're filtering the list of projects to a certain selection. But what would happen if you started creating more repositories and the ones you want to display are no longer returned because GitHub's API paginates the list of repositories? Since you already know the names of the repositories you want to include you could also use this endpoint to retrieve them individually. This is also a good way to experiment a bit with concurrent requests using Promise.all

create CSS

• CSS
• style transitions

create HTML

• HTML
• create div for the repo-cards

githubapi

• create handler
• create listener
• create class
• create render function

---

• create data
• create social preview for a selection of repos

create loggers

• use the logger functions
• use Jsdoc

create documentation

• create a backlog
• create development-strategy
• fill the README