This all started from personal wish to try GraphQL, to see how it works, to code something, and then make a decision, based on own experience. I also tend to grasp new technologies, as fast as I can, and that is why this project dedicated to new things, at least some first touch.
GitHub API, REST vs. GraphQL, XmlHttpRequest vs. Fetch API, HTML5
template, ES6 String Literals, ES2017
async/await, URLSearchParams API, Chrome Canary, NodeJS, npm vs. bower, Bootstrap
v4-dev, Pace progress bar, OAuth vs. Auth0, deployment to Heroku.
I was working on set of work-related tasks and personal sandbox projects, and I came up with task idea:
Get list of GitHub repositories based on my custom data about owner and name.
But here, I will share my experience about working directly with GitHub API, with their version 3 (REST-based) and version 4 (GraphQL-based).
UPD: 😦 It’s not fixed/resolved. I created a new comment to one of issues, received email, then accidentally clicked “Mute” and went to the page.A bit later, checked Notifications page – again the same. But then re-subscribed/watched. Did not help right away.A bit later, refreshed the page – Notifications alive. No idea what is happening.
It’s been a while, since I started seeing warning about errors on Notifications page on GitHub. I was more than sure, it’s due to my huge list of watched repositories. As fallback page on GitHub says, I tweeted to support, but none answered.
During my work on web project for US client, I faced with interesting issue, which at the first look seemed to be related to D3.js/C3.js donut charts, but after deep debugging, I discovered it’s because of nature of Underscore.JS 1.6.0 library/code. I would say, it’s bright example of the fact how important to know main purpose of dedicated API/tool, and implement custom codebase for the future to be working also correct.
Since I use GIT, during my daily work, I always face with some edge cases. This post is about to list such cases in one place. I collected set of situations, verified on practice.
Since that time, when my eyes saw Git, I wrote lot of code. I studied Git on practice, on live examples. I wrote 3 articles here on my blog. I shared knowledge with my team mates. So goals of this particular article are:
- collect all my experience.
- classify commands for myself and other readers by similarity in use and frequency of usage.
- minimized explanation, due to the fact, that on web site https://git-scm.com/ or simply Googling, you can find more details.
- this will be placeholder for future updates (I will add some new item from my work life).