| { | |
| "agent_servers": { | |
| "OpenCode": { | |
| "command": "opencode", | |
| "args": ["acp"] | |
| } | |
| } | |
| } |
| const formData = { foo: "foo", bar: "M&Ms" }; | |
| // Good 🔥 | |
| const postBody = Object.keys(formData) | |
| .map((key) => encodeURIComponent(key) + "=" + encodeURIComponent(body[key])) | |
| .join("&"); | |
| // Better 🔥🔥 | |
| const postBody = Object.entries(formData) | |
| .map(([key, value]) => `${encodeURIComponent(key)}=${encodeURIComponent(value)}`) |
| import { pipe } from 'fp-ts/pipeable' | |
| import * as O from 'fp-ts/Option' | |
| import * as Op from 'monocle-ts/lib/Optional' | |
| import * as r from 'rxjs' | |
| import * as ro from 'rxjs/operators' | |
| import { createStore, applyMiddleware } from 'redux'; | |
| import { createEpicMiddleware } from 'redux-observable'; | |
| import React from 'react'; | |
| import { Provider, useDispatch, useSelector } from 'react-redux'; | |
| import { makeADT, ofType, ADTType } from '@morphic-ts/adt' |
This gist will no longer be updated as the changelog will be on the official website.
Converted via https://domchristie.github.io/turndown
| // cypress/support/hooks.js | |
| // Cypress does not support listening to the fetch method | |
| // Therefore, as a workaround we polyfill `fetch` with traditional XHR which | |
| // are supported. See: https://github.com/cypress-io/cypress/issues/687 | |
| enableFetchWorkaround() | |
| // private helpers | |
| function enableFetchWorkaround() { | |
| let polyfill |
| import { h, cloneElement, Component } from 'preact'; | |
| /** Example <Fetch url="/foo.json" /> compositional component. | |
| * Just to demonstrate a compositional component that requires input massaging. | |
| */ | |
| class Fetch extends Component { | |
| state = { loading: true }; | |
| componentDidMount() { | |
| this.update(); |
What is transduce? What is it for? This document is intended to help people (such as myself) who would be looking through the ramda docs, find transduce and have no idea if it would be a good fit for my current problem.
All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.
Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.
elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent
You don't really need a framework or fancy cutting-edge JavaScript features to do two-way data binding. Let's start basic - first and foremost, you need a way to tell when data changes. Traditionally, this is done via an Observer pattern, but a full-blown implementation of that is a little clunky for nice, lightweight JavaScript. So, if native getters/setters are out, the only mechanism we have are accessors:
var n = 5;
function getN() { return n; }
function setN(newN) { n = newN; }
console.log(getN()); // 5
setN(10);