hendrikniemann

// TODO: Skip tables without an id field?
module.exports = function LoadByIdsPlugin(builder) {
  builder.hook('GraphQLInputObjectType:fields', (fields, build, context) => {
    const {
      scope: { isPgCondition, pgIntrospection: table },
      fieldWithHooks,
    } = context;
    if (!isPgCondition || !table || table.kind !== 'class') {
      return fields;
    }

stephensauceda

/* 
 *    Steps
 * 1. Rename your gulpfile.js to gulpfile.babel.js
 * 2. Add babel to your package.json (npm install -D babel)
 * 3. Start writing ES6 in your gulpfile!
 */
 
 import gulp from 'gulp'; // ES6 imports!
 import sass from 'gulp-sass';
 

fversnel

var cloneWithProps = React.addons.cloneWithProps;

var SmartSortable = React.createClass({
  getDefaultProps: function() {
    return {component: "ul", childComponent: "li"};
  },

  render: function() {
    var props = jQuery.extend({}, this.props);

rtt

Tinder API documentation

Note: this was written in April/May 2014 and the API may has definitely changed since. I have nothing to do with Tinder, nor its API, and I do not offer any support for anything you may build on top of this. Proceed with caution

http://rsty.org/

I've sniffed most of the Tinder API to see how it works. You can use this to create bots (etc) very trivially. Some example python bot code is here -> https://gist.github.com/rtt/5a2e0cfa638c938cca59 (horribly quick and dirty, you've been warned!)

zsup

Documentation-Driven Development

The philosophy behind Documentation-Driven Development is a simple: from the perspective of a user, if a feature is not documented, then it doesn't exist, and if a feature is documented incorrectly, then it's broken.

• Document the feature first. Figure out how you're going to describe the feature to users; if it's not documented, it doesn't exist. Documentation is the best way to define a feature in a user's eyes.
• Whenever possible, documentation should be reviewed by users (community or Spark Elite) before any development begins.
• Once documentation has been written, development should commence, and test-driven development is preferred.
• Unit tests should be written that test the features as described by the documentation. If the functionality ever comes out of alignment with the documentation, tests should fail.
• When a feature is being modified, it should be modified documentation-first.
• When documentation is modified, so should be the tests.

hfcorriez

var mongoose = require('mongoose');
var db = mongoose.createConnection('127.0.0.1', 'test');

// Make schema
var schema = mongoose.Schema({ name: String });

// Create subscribers collection
var subscribers = [];

// Hook `save` post method

SQLyogTunnel.php

<?php

/*
    SQLyog
    Copyright 2003-2006, Webyog
    http://www.webyog.com    
    
    HTTP Tunneling Page
    
    This page exposes the MySQL API as a set of web-services which is consumed by SQLyog - the most popular GUI to MySQL.