brandur

  def replace_vars(text, vars)
    updated_lines = []

    text.each_line do |line|
      new_line, after_func = line.split("func(", 2)
      vars.each do |var|
        new_line.gsub!(/([^"]?\b)#{var}\b/, '\1' + "bundle.#{var}")
      end

      new_line += "func(" + after_func if after_func

brandur

module github.com/brandur/prequire

go 1.19

require github.com/stretchr/testify v1.8.1

require (
	github.com/davecgh/go-spew v1.1.1 // indirect
	github.com/pmezard/go-difflib v1.0.0 // indirect
	gopkg.in/yaml.v3 v3.0.1 // indirect

brandur

# typed: strict
# frozen_string_literal: true

require "base32"
require "securerandom"
require "ulid"

# A type to represent UUIDs. Particularly useful for annotating fields in API
# representations or Sorbet parameters to help prevent accidentally mixing up
# UUIDs and EIDs as they're being passed around as loose strings.

brandur

require 'kramdown'
require 'redcarpet'
require 'toml'
require 'yaml'

#
# pool
#

class WorkerPool

brandur

#!/usr/bin/env ruby

#
# Downsizes and optimizes (for size) an image so that it can be suitably/easily
# sent to people via email.
#

TARGET_DIR = "#{Dir.home}/Downloads"
TARGET_WIDTH = 2000

brandur

Overall: very good experience. My migration from Travis involved quite a few prerequisites to get everything working in the same way again, and I was pleased to find all of them available in some form on GitHub Actions.

Here a couple problems I ran into:

• Although there's a story for running background services like Postgres, there doesn't seem to be much of one for interacting with them with client tooling. After Postgres is running, I often want to createdb or raise a schema with psql. I ended up installing postgres via apt-get to get these tools, but it's mostly just good luck that the version drift between these old LTS versions and Postgres running in my container hasn't been too great for things not to work.

• The above is true for all command line utilities. If I want Imagemagick, I have the choice between (1) Ubuntu's ancient version, and (2) running everything through a Docker container, and

brandur

[
    //
    // Ctrl + j/k for up/down in ALL the places
    //
    {
        "key": "ctrl+j",
        "command": "cursorDown",
        "when": "textInputFocus"
    },
    {

brandur

package main

import (
	"bytes"
	"fmt"
	"io/ioutil"
	"net/http"
)

func main() {

brandur

// This example is similar to candidate #2, but compiles because we make sure
// to define an alternate type for int64 (Int64) that we're allowed to add the
// Convert function to.
//
// This approach works, and is fairly clever, but ergonomically it looks very
// similar to the pointer approach in candidate #1. You use a type conversion
// instead of a function call when invoking Int64, but they look identical in
// code.
//
// Arguably, it has a small advantage over pointers in that because Int64 here

brandur

// This example is similar to candidate #2, but compiles because we make sure
// to define an alternate type for int64 (Int64) that we're allowed to add the
// Convert function to.
//
// This approach works, and is fairly clever, but ergonomically it looks very
// similar to the pointer approach in candidate #1. You use a type conversion
// instead of a function call when invoking Int64, but they look identical in
// code.
//
// Arguably, it has a small advantage over pointers in that because Int64 here