A Go Repo and Some Go Code [Video]
See the original posting on DZone Python
Wrapped up another Twitch stream (follow here) and streamed live via YouTube where the video is now (subscribe here, video here). However, the more interesting part, in my opinion, was where I broke down a few key parts of the application building features around file writes, reads, JSON marshaling, and some other functionality. I also put together a repo of the code I used here on Github (code shown and explained below). I dove into this topic in the later part of the stream which I’ve time tagged below. For the full timeline and the rest of the video just watch from the beginning. I do make some progress working on Colligere, but I’ll cover that topic in a subsequent blog entry and Twitch stream.
- 1:32:40 – Creating a new application with Jetbrains Goland to show off how to use the Go core libraries around the user, JSON, and some basic file creation and writing.
- 1:36:40 – At this point, I start adding some basic code to pull the current user and collect some information about that user.
- 1:40:42 – I extract the error code using the Goland refactoring feature and set up a
func check()for error checking. That cleans up the inline code a bit.
- 1:43:10 – Here I add to the user data retrieved some environment variables to that list of collected data. I also cover again, as I have a number of times, how the environment variables are pulled in IDE versus user session versus out of IDE.
- 1:47:46 – Now I add a file exist, check, and start working on that logic.
- 1:48:56 – Props to Edd Turtle on a solid site on Go. Here’s the blog entry, and respectively the path to more of Edd’s material @ https://golangcode.com/. Also, Edd seems like a good guy to follow @eddturtle.
- 2:01:33 – Starting the JSON Work here to marshal and unmarshall.
- 2:26:33 – At this point, I push the code up to GitHub (repo here) using the built-in Goland VCS features. I realize I’ve named the repo "adron" by accident so I rename it, close Goland, and then clone the code back down locally with Goland’s VCS features. It’s kind of interesting to see Goland go through the two-factor auth for this too.
- 2:58:56 – The Seattle Thrashing Code outtro!
There were a few notes I took during the session with my collected links and references for things I looked up. Those included the following: