calebmer

Caleb’s Open Source Software Feature Wishlist

Every once and a while there will be a feature in open source software that I (Caleb) want, but needs a PR to implement. This document is a collection of issues around such features. This list is to track such features and allow me, or others, to find issues to fix whenever the time and interest arises.

Some issues will be easier than others, but hopefully all are more then possible given an afternoon. Ideally the issue has enough context to get rolling.

• jsx-eslint/eslint-plugin-react#241

calebmer

declare module 'react-hot-loader' {
  import React = __React

  interface AppContainerProps {
    children?: React.ReactElement<any>
  }

  export class AppContainer extends React.Component<AppContainerProps, {}> {}
}

calebmer

{
  luke: person(id: \"cGVvcGxlOjE=\") {
    height
    mass
    species {
      name
      classification
    }
  }
}

calebmer

This document is a work in progress. Any comments would be extremely helpful and appreciated!

PostgREST Auth Protocol

This document will describe an authentication framework very loosely based on the OAuth2 specification for a seperate authentication server to be used with the main PostgREST resource server. As PostgREST is going in a layered direction, this authentication layer must be interchangeable with other authentication implementations.

Options

• The first parameter (same as PostgREST) must be a PostgreSQL database connection string.
• -p, --port [number]: The port on which the server will listen for HTTP requests. Defaults to 3001.
• -u, --user-relation [relation]: The relation (table or view) which PostgREST Auth will use for generating JWTs. If the relation is a view, it is recommend that it be auto-updateable. Must be user defined. The default is postgrest.users.
• -r, --refresh-relation [relation]: The relation where PostgREST Auth will st

calebmer

For more resources on JSON hyperlink schemas, see:

• The spec.
• Brandur's introductory article.
• JSON Schema reference.
• Heroku's JSON Schema API documentation and production schema (make sure to use a application/vnd.heroku+json; version=3 accept header).

calebmer

CREATE SCHEMA private;

CREATE TABLE private.person (
  id               serial PRIMARY KEY,
  email            varchar(128) NOT NULL UNIQUE CHECK ( email ~* '^.+@.+\..+$' ),
  given_name       varchar(64) NOT NULL CHECK ( LENGTH(given_name) >= 2 ),
  family_name      varchar(64) CHECK ( LENGTH(family_name) >= 2 ),
  image            varchar(128),
  created_at       timestamp NOT NULL DEFAULT NOW(),
  password_hash    char(60)

calebmer

'use strict'

var http = require('http')
var request = require('supertest')
var Router = require('router')
var finalhandler = require('finalhandler')

var N = parseInt(process.env.N, 10)
var router = Router()

calebmer

/*
 * Next generation of building HTTP apps in NodeJS. Implements the HTML
 * streaming API through ES6 generators. ES7 async functions are used to fetch
 * data.
 *
 * Why is this a good idea?
 * 1) It is beautiful. You setup a consistent API backend and your frontend
 *    backend (tongue twister) just looks like this. Layout implementations
 *    would be a bit odd, but it harkens back to plain old PHP 'require's.
 * 2) Most modern, ES6, ES7, streams. All the new pretties.

calebmer

Iteration(s):            0
==================================
Object.create:           0
Object.setPrototypeOf:   0

Iteration(s):            1
==================================
Object.create:           0
Object.setPrototypeOf:   0.04

calebmer

// ==================
// Misc
// ==================

$infinity: 9999;

@mixin clearfix() {
  &:before,
  &:after {
    content: "";