Justin Wehrman wehrhaus

In this gist I would like to describe an idea for GraphQL subscriptions. It was inspired by conversations about subscriptions in the GraphQL slack channel and different GH issues, like #89 and #411.

Conceptual Model

At the moment GraphQL allows 2 types of queries:

query
mutation

Reference implementation also adds the third type: subscription. It does not have any semantics yet, so here I would like to propose one possible semantics interpretation and the reasoning behind it.

	module.exports = {
	"env": {
	"browser": true
	},
	"extends": "eslint:recommended",
	"globals": {
	"angular": true,
	"console": true,
	"Core": true
	},

	const createStore = (reducer) => {
	let state;
	let listeners = [];

	const getState = () => state;

	const dispatch = (action) => {
	state = reducer(state, action);
	listeners.forEach((listener) => listener());
	};

	#!/usr/bin/env node

	console.log(
	`
	FILENAME: transform-json.pl

	#!/usr/bin/perl
	#
	# Takes a list of environment variables and applies
	# - the values to the json files matching keys

	'use strict';

	import BaseCollection from './data/collections/BaseCollection';
	import * as _ from 'lodash';

	RequestPool.$inject = ['$q'];

	export default function RequestPool($q) {
	function RequestPool(cap) {
	this.cap = cap;

	function* range(start, end) {
	yield start;
	if (start === end) return;
	yield* range(start + 1, end);
	}

	const createRange = (a, b) => [...range(a, b)];

	// Example Usage: Create array of lowercase alphabet
	const alphabet = createRange(97, 122).map(k => String.fromCharCode(k));