tomhicks

function useTaskQueue(params: {
  shouldProcess: boolean
}): {
  tasks: ReadonlyArray<Task>
  isProcessing: boolean
  addTask: (task: Task) => void
} {
  const [queue, setQueue] = React.useState<{
    isProcessing: boolean
    tasks: Array<Task>

danieleggert

GPG and git on macOS

Setup

No need for homebrew or anything like that. Works with https://www.git-tower.com and the command line.

1. Install https://gpgtools.org -- I'd suggest to do a customized install and deselect GPGMail.
2. Create or import a key -- see below for https://keybase.io
3. Run gpg --list-secret-keys and look for sec, use the key ID for the next step
4. Configure git to use GPG -- replace the key with the one from gpg --list-secret-keys

ryanflorence

import React from 'react'

const provideContext = (contextKey, contextType) => (
  React.createClass({
    childContextTypes: {
      [contextKey]: contextType
    },

    getChildContext() {
      const { children, ...props } = this.props

mdouglass

{
  "presets": [
    "es2015"
  ],
  "plugins": [
    "transform-runtime",
    "transform-export-extensions"
  ]
}

jamiebuilds

export lint from './task-lint';
export test from './task-test';
export build from './task-build';
export dev from './task-dev';

export default dev;

rgrove

"use strict";

var _   = SM.import('lodash');
var DOM = SM.import('sm-dom');
var Uri = SM.import('sm-uri');

// WebKit (as of version 538.35.8) fires a useless popstate event after every
// page load, even when the page wasn't popped off the HTML5 history stack. We
// only want to handle popstate events that result from a page actually being
// popped off the HTML5 history stack, so we need a way to differentiate between

toumorokoshi

module.exports = function(grunt) {

    // Project configuration.
    grunt.initConfig({
        pkg: grunt.file.readJSON('package.json'),
        jshint: {
            myproject: {
                files: [
                    { src: ['myproject/static/source/myproject/js/**/*.js'] }
                ]

clarle

ModelList Re-write

Goals and Current Usage

The goal in re-writing ModelList is to take advantage of the features in LazyModelList which improve performance, which is mainly to not immediately regenerate plain JavaScript objects that are added to the ModelList.

Right now, a ModelList is sometimes used like this inside a View:

template: function(data, options) {
 /* Interpolates data into a string of HTML */

caridy

What is this?

This is a script that you can add to your application to generating yui meta data and compiling yui modules using express-yui and locator. As a result, a build folder will be generated with everything that was compiled.

How does this work?

Locator walks the folder structure for your app, and finds any yui module, including build.json or just traditional *.js files with the corresponding YUI.add() statement. Generating the result of the operation as well as the metadata associated to each module.

Under the hood, it uses shifter to generate almost everything that is needed.

tivac

/*jshint browser:true, yui:true */
YUI.add("plugin-lazy-images", function(Y) {
    "use strict";
    
    var plugins    = Y.namespace("GW2.Plugins"),
        LazyImages;
    
    LazyImages = Y.Base.create("lazyImages", Y.Plugin.Base, [], {
        // Y.Base lifecycle fns
        initializer : function() {