The post title "Test whether variable is a number" looks like a trivial question, but let's dig deeper and try to cover all edge cases. I will split it into two problems and will cover them separately.
The basic example from the official documentation is very informative (this is not a sarcasm). I just want to add my 2 cents in order to make it more es6 like, then it is now. Plus I want one function of initialization that will take care of everything. I want to be able to run it from anywhere in the code and be sure that app will be authorized.
Once upon a time I needed to create UUIDs, and I needed to do it manually. On the internet you can find a bunch of solutions, and you don't really need to invent anything. The tech is relatively easy and there is no room for engineering innovation, so I decided to dig into user experience.
It's not that hard to use graphql with go, but it could take some effort to find all the gotchas. Therefore let's save some time and talk about some configuration of graphql in Golang.
In this tutorial I'll use graphql-go/graphql library, version v0.7.9
More than once I argued with my fellow developers on whether we should hide or disable some feature or functionality. I decided to write down my opinion to be sure the internet knows.
Sorry, but documentation of auth0 is not the best source of knowledge on how to use auth0. Not something that you expect to happen, right? Official documentation is okay if you need to understand only a basic usage, but if you need more than that, you pretty much on your own. At least it's my experience with this service. Especially for not so popular topic of "renewing auth0 token for SPA (Single Page Application)". So let's talk about exactly that.
Ok, first of all I'm assuming you know what Redux is and already used it in one of your projects. Now, after we established that, let's move on. I always prefer to be clear in my assumptions and intentions. It makes life much easier :)
Yeah, I know, another library. But that's okay, we'll go through all of them and we'll find the best one for each project. Or at least this is something that we should do as responsible developers.
I'm using a lot of git features via CLI. Mainly it's rebasing, committing and pushing new changes to the repository. I know that most editors have UI solutions for these commands, but I never liked it and honestly don't see any reason to change my habits. Stubborn you say? Probably. Don't know.