samselikoff

function brush() {
    // Use x.domain to filter the data, then find the max and min duration of this new set, and set y.domain to that
    x.domain(brush.empty() ? x2.domain() : brush.extent());
    var dataFiltered = data.filter(function(d, i) {
        if ( (d.date >= x.domain()[0]) && (d.date <= x.domain()[1]) ) {
            return this;
        }
    })
    var buildersFiltered = color.domain().map(function(name) {
        return {

samselikoff

{"lastUpload":"2020-05-01T19:06:41.818Z","extensionVersion":"v3.4.3"}

samselikoff

import { ReactNode, useLayoutEffect, useRef } from 'react';

const keyframes = `
  @keyframes spinner {
    0% { opacity: 1; }
    100% { opacity: 0; }
  }
`;

export default function Spinner({

samselikoff

This post is also on my blog, since Gist doesn't support @ notifications.

---

Components are taking center stage in Ember 2.0. Here are some things you can do today to make the transition as smooth as possible:

• Use Ember CLI
• In general, replace views + controllers with components
• Only use controllers at the top-level for receiving data from the route, and use Ember.Controller instead of Ember.ArrayController or Ember.ObjectController
• Fetch data in your route, and set it as normal properties on your top-level controller. Export an Ember.Controller, otherwise a proxy will be generated. You can use Ember.RSVP.hash to simulate setting normal props on your controller.

samselikoff

import * as d3 from "d3";
import {
  eachMonthOfInterval,
  endOfMonth,
  format,
  isSameMonth,
  parseISO,
  startOfMonth,
} from "date-fns";
import useMeasure from "react-use-measure";

samselikoff

const plugin = require("tailwindcss/plugin");

module.exports = {
  mode: "jit",
  purge: {
    content: ["./src/**/*.{js,ts,jsx,tsx,mdx,vue}"],
  },
  theme: { extend: {} },
  variants: {},
  plugins: [

samselikoff

{
  "diffEditor.renderSideBySide": true,
  "editor.fontSize": 14,
  "editor.lineHeight": 22,
  "editor.tabSize": 2,
  "editor.matchBrackets": "never",
  "editor.cursorBlinking": "solid",
  "editor.selectionHighlight": false,
  "editor.occurrencesHighlight": "off",
  "editor.scrollbar.horizontal": "hidden",

samselikoff

[
  {
    "key": "ctrl+k",
    "command": "editor.action.moveLinesUpAction",
    "when": "editorTextFocus && !editorReadonly"
  },
  {
    "key": "alt+up",
    "command": "-editor.action.moveLinesUpAction",
    "when": "editorTextFocus && !editorReadonly"

samselikoff

Remix's useFetcher doesn't return a Promise for any of its methods (like fetcher.submit()) because Remix doesn't want you to explicitly await anything so they can handle things like cancellation for you. Instead, they recommend adding a useEffect and performing whatever logic you need to after the fetcher is in a particular state.

I found using an effect to run some logic after a submission to be too indirect, and there seem to be plenty of cases where you want to submit a form and then perform some other work on the client (sometimes async, like requesting the user's permission for their location), and I'd rather just do that after a submission in the event handler rather than an effect.

So here's a proof of concept hook that wraps Remix's useFetcher and returns a version of submit that is a promise, and resolves with the data from the action:

function useFetcherWithPromise() {
  let resolveRef = useRef();
  let promiseRef = useRef();

samselikoff

Version 1

import { useActionState } from "react";

async function addToCart(itemId) {
  'use server'

  if (db.add(itemId)) {
    return "success"