oauth2 VS Wails

The guide covers setting up GitHub, using the golang.org/x/oauth2 package, and handling OAuth authentication. The code snippets are easy to follow and can be modified to fit your project's needs.

I personally use golang.org/x/oauth2 to handle OAuth in my app, so I'll use that for this example.

I mean using the OAuth2 client library that's maintained as part of the Go project.

My wife sent MR into golang oauth2 library https://github.com/golang/oauth2/pull/450

Hmm, this might be a relevant issue: https://github.com/golang/oauth2/issues/128 . On the face of it, it looks like https://github.com/coreos/go-oidc is a more thorough implementation...(?)

Handling auth in a Transport is a common pattern, that's what x/oauth2 does for example: https://github.com/golang/oauth2/blob/master/transport.go#L20

golang/oauth2 (Go): Go OAuth2

This is basically the same tech stack of an app I’ve been planning to build, but deployed as a desktop application using Wails: https://github.com/wailsapp/wails

Wails 2.6k

The wails project does this when. You can check it out here https://github.com/wailsapp/wails/blob/master/v2/internal/typescriptify/typescriptify.go for inspection.

I have built Web front-ends (React or Svelte) with Go-backend. Embed in a web-view to make it a native desktop app, or get funky and give it native chrome/menus etc. [Wails](https://github.com/wailsapp/wails) is a good candidate to start if you want to cut on boiler plate.

Is that what wails is doing here? (On mobile)

In a "local" environment, where an executable can be provided to someone with the entire game contents. In this case, the game won't use WebSockets, and will instead use a Go/JS bridge (something like Wails) to connect.

Have you seen wails? https://github.com/wailsapp/wails

You should check out https://github.com/wailsapp/wails/pull/1959