jsumners

Let's see what happens with achors in a markdown table.

Toc

• foo

nonsense

A bunch of nonsense to elongate the viewport.

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Quisque sed nisl volutpat, molestie nisl et, convallis lorem. Ut varius at massa quis ultricies. Duis nec dolor ut risus sagittis pretium. Suspendisse malesuada quam ac tortor pulvinar, vitae iaculis tellus euismod. Nullam faucibus sapien quis libero auctor iaculis. Proin rhoncus vel elit nec fringilla. Aliquam bibendum, ligula et rutrum hendrerit, ligula urna pulvinar ex, in pellentesque ante tortor et sem. Class aptent taciti sociosqu ad litora torquent per conubia nostra, per inceptos himenaeos. In viverra ipsum quam, nec finibus nisi tempor in. Pellentesque porta dictum sem non tincidunt. Phasellus ut justo euismod, auctor nulla et, aliquet lorem. Vivamus metus ante, dignissim ac fermentum a, rhoncus id erat. Ut tincidunt tortor non laoreet bibendum. Nam in pharetra orci, vitae lobortis purus.

jsumners

Tools:

• https://www.mock-server.com

Sites:

• http://httpbin.org
• http://httpbin.io
• https://httpbingo.org
• https://reqbin.com
• https://jsonplaceholder.typicode.com
• https://reqres.in (supports paging)

jsumners

import dotenv from "dotenv";
dotenv.config();

// Create a .env file in the same directory
// as this script. Add the following constants
// to that file:
const ORG = process.env.ORG;
const REPO = process.env.REPO;
const GITHUB_TOKEN = process.env.GITHUB_TOKEN;

jsumners

'use strict'

class Foo {
  static createFoo() {
    return new Foo()
  }
}

class Bar {
  static createBar() {

jsumners

What are Migrations

Just like how we use Git to version control source code, we use migrations to manage the state of our database schemas.

I'm not really sure what that means...

Imagine you're working on project with another developer, and you're both tasked with creating a specific part of an event planning application. Let's say you are in charge of creating the Users and your friend is going to create the Events.

Let's say you and your friend divided the work in a way so that neither of you will have to to use each other's code to finish your tasks. While you're working on your part of the application, you only really need to touch the Users table when you are working with the database.

Creating models and migrations

jsumners

# Based on https://gist.github.com/kmatt/71603170556ef8ffd14984af77ff10c5
# prompt ">" indicates Powershell commands

# https://docs.microsoft.com/en-us/windows/wsl/install-win10

> dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart
> dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart

# install https://wslstorestorage.blob.core.windows.net/wslblob/wsl_update_x64.msi

jsumners

# {{ansible_managed}}

{% if 'vmware' in ansible_product_name|lower %}
# Disable panic quit if system is >1000s out of sync because VMware.
tinker panic 0
{% endif %}

# Permit time synchronization with our time source, but do not
# permit the source to query or modify the service on this system.
restrict default kod nomodify notrap nopeer noquery

jsumners

import dotenv from "dotenv";
dotenv.config();

const ORG = process.env.ORG;
const GITHUB_TOKEN = process.env.GITHUB_TOKEN;

import { Client } from "undici";

const client = new Client("https://api.github.com");
const headers = {

jsumners

Ocassionally, someone will start a pull request and, for various reason, not see it through. Later, someone else may wish to finish that work. Even though the original author was unable to finish their work, we should still include their efforts in our project's history. To do so, the person wishing to finish the original pull request should start their new pull request using the original as the base.

The simplest workflow to accomplish this is:

$ # For the project on GitHub to your account and then:
$ git clone 

jsumners

import fs from 'fs/promises';
import treeify from 'treeify';

const result = await readModDir('.');
console.log(treeify.asTree(result, true));

async function readModDir(modDirPath) {
  const dirEntries = await fs.readdir(new URL(modDirPath, import.meta.url));
  const hasNodeModules = dirEntries.some(entry => entry === 'node_modules');
  const pkgSrc = await fs.readFile(new URL(`${modDirPath}/package.json`, import.meta.url));