This is a brief introduction to the tools needed to maintain a personal fork of ZMK (or QMK or really whatever). It covers:
import React from 'react'; | |
import { render } from '@testing-library/react'; | |
import { queryAllByTableHeader } from './tables'; | |
describe('table testing utils', () => { | |
it('test', () => { | |
render( | |
<div role="region" aria-labelledby="caption-id"> | |
<table> |
Composition of <Route>
elements in React Router is changing in v6 from how it worked in v4/5 and in Reach Router. React Router v6 is the successor of both React Router v5 and Reach Router.
This document explains our rationale for making the change as well as a pattern you will want to avoid in v6 and a note on how you can start preparing your v5 app for v6 today.
In React Router v5, we had an example of how you could create a element](https://github.com/remix-run/react-router/blob/320be7afe44249d5c025659bc00c3276a19f0af9/packages/react-router-dom/examples/Auth.js#L50-L52) to restrict access to certain routes on the page. This element was a simple [wrapper around an actual
element that made a simple decision: is the user authenticated or not? If so, ren
function run(input, parameters) { | |
const appNames = []; | |
const skipAppNames = []; | |
const verbose = true; | |
const scriptName = "close_notifications_applescript"; | |
const CLEAR_ALL_ACTION = "Clear All"; | |
const CLEAR_ALL_ACTION_TOP = "Clear"; |
#!/usr/bin/env node | |
// Generates renovate config to fix @types and package running out of sync | |
// See https://github.com/renovatebot/renovate/issues/4893 | |
const path = require("path"); | |
const fs = require("fs"); | |
// This script lies under scripts/update-renovate.js, therefore the .. | |
const renovatePath = path.resolve(__dirname, "../renovate.json"); |
import * as React from 'react'; | |
/** | |
* React.Ref uses the readonly type `React.RefObject` instead of | |
* `React.MutableRefObject`, We pretty much always assume ref objects are | |
* mutable (at least when we create them), so this type is a workaround so some | |
* of the weird mechanics of using refs with TS. | |
*/ | |
export type AssignableRef<ValueType> = | |
| { |
#!/bin/bash | |
# | |
# Inspects branch name and checks if it contains a Jira ticket number (i.e. ABC-123). | |
# If yes, commit message will be automatically prepended with [ABC-123]. | |
# | |
# Useful for looking through git history and relating a commit or group of commits | |
# back to a user story. | |
# |
import { Machine, assign } from 'xstate'; | |
import firebase from './firebase'; | |
const chart = { | |
id: 'auth', | |
context: { | |
auth: null, | |
error: null, | |
loggedoutTime: null | |
}, |
This gist is an ES module which provides functions to import and export data from an IndexedDB database as JSON. It's based on Justin Emery's indexeddb-export-import
package, but applies some adjustments that reflect better on the current browser landscape (i.e. better developer ergonomics but no support for Internet Explorer).
For each of the provided functionalities, you need a connected IDBDatabase
instance.
import { idb } from 'some-database'
{ | |
sourceMaps: false, | |
comments: false, | |
plugins: [ | |
["plg-one", {}], | |
["plg-two", {opt: false}], | |
], | |
env: { | |
development: { | |
sourceMaps: true, |