kendallroth

option explicit
On Error GoTo 0
'Dim sResult: sResult = Wscript.ScriptName     ''' debugging

Const HKEY_CURRENT_USER = &H80000001

Dim strComputer, strKeyPath, strValName, dwValue, arrValues, objReg, WshShell
arrValues = Array (" unknown", " show hidden files", " hide hidden files" )
strComputer = "."

kendallroth

Print GitHub Markdown

Either create a browser snippet or execute from console:

var content = document.querySelector('.markdown-body');
var body = document.querySelector('body');
body.innerHTML = '';
body.appendChild(content);

kendallroth

"""""""""""""""""""""""""""""""""""""""""""""""""""
" 01. General
""""""""""""""""""""""""""""""""""""""""""""""""""
set nocompatible
filetype off

""""""""""""""""""""""""""""""""""""""""""""""""""
" 02. Vundle plugins
""""""""""""""""""""""""""""""""""""""""""""""""""
set rtp+=~/.vim/bundle/Vundle.vim

kendallroth

/**
 * Dynamically sets a deeply nested value in an object (returns new object)
 *
 * NOTE: By default it will create any missing nested keys!
 *
 * @param   obj       - Object which contains the value to set
 * @param   path      - Path to nested key being set
 * @param   value     - Target value to set
 * @param   recursive - Whether to create non-existing paths
 * @returns Updated nested object

kendallroth

Jupyter Git Conflicts

Jupyter Notebooks have a tendency to cause Git conflicts when working collaboratively on a notebook. This is primarily due to cell metadata that really doesn't matter, and can be removed with a pre-save configuration hook. This hook will be run across all Jupyter Notebooks; however, it utilizes a custom opt-in metadata configuration option (reduce_git_conflicts). If the opt-ine is not specified, or set to false, the Notebook will save as normal.

1. Add pre-save hook to Jupyter Notebook config
2. Enable reducing Git conflicts in Notebook metadata

NOTE: This approach does modify the notebook save file itself, which could lead to issues if there are fields that must remain in the file but lead to conflicts (and would otherwise be removed).

NOTE: This approach was developed with Jupyter Notebook in mind. While Jupyter Lab is quite similar, there are several differences (generating config, editing metadata).

kendallroth

type CacheKey = string | number;

interface Cache<T> {
  /** Number of cache entries */
  readonly count: number;
  /** Get an item from the cache */
  get: (key: CacheKey) => T | null;
  /** Check whether cache contains a given item */
  has: (key: CacheKey) => boolean;
  /** Cached items */

kendallroth

Typing RHF Fields

While react-hook-form supports strong typing everywhere, including support for types inferred from a Yup schema (Yup.InferType<Schema>), passing field names to controls is still untyped. However, this can be resolved with RHF's FieldPath type and a helper function.

Options

// Option 1: Declared per form, less boilerplate per control
export const getOrganizationFormField = (name: FieldPath<OrganizationForm>) => name;
getOrganizationFormField("billingAddress.address1");

kendallroth

Some projects may have files that should be skipped in Git diff but still show in Git status (and be tracked). This can be made possible with a custom diff driver that uses a no-op command.

Adapted from StackOverflow - @KurzedMetal.

Custom diff driver

Create a global no-op diff command driver with the following command. Note that driver can be limited to local respository by removing the --global flag.

git config diff.nodiff.command /bin/true

kendallroth

CS2 Modding: JS deobfuscation

For anyone else working on understanding some of the JS helpers for the Colossal Order UI package, I spent some time deobfuscating a couple functions/classes. Please note there certainly be mistakes and there is some omitted code; however, overall the gist is present.

kendallroth

Upgrading to v23

Upgrading to Pocketbase v23 was a large undertaking due to the amount of fundamental changes to extending as a framework. The library contains several excellent resources, including the GitHub Release and Pocketbase Upgrade Guide, that help with the upgrade. However, they do not explain how to handle upgrading deployed/production instances, which is a bit more tricky depending on the server host. This guide deals with upgrading a Pocketbase application deployed on Pockethost, an excellent and affordable hosting service for Pocketbase apps.

Official Upgrade Guide

The Pocketbase Upgrade Guide provides an excellent guide to the major breaking changes. However, there were a few assorted changes not explicitly documented (and there may be others still).

Email templates no longer have ACTION_URL

Email templa