Matheus Correia matheuscorreia

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.

Commit Message Format

This specification is inspired by and supersedes the [AngularJS commit message format][commit-message-format].

We have very precise rules over how our Git commit messages must be formatted. This format leads to easier to read commit history.

Each commit message consists of a header, a body, and a footer.

	const dateRangeDefinition = {
	begin: MomentParam,
	end: MomentParam,
	};
	const DateRangeParam = getSchemaParam(dateRangeDefinition);

	const decoded = FilterParam.decode('begin-2019-05-19T03:00:00.000Z_end-2019-05-19T03:00:00.000Z');

	const decoded = {
	begin: moment('2019-05-19T03:00:00.000Z'),

	import React from 'react';
	import { mount } from 'enzyme';

	import formEventEmitter from '../formEventEmitter';
	import MyFunctionComponent from '../MyFunctionComponent';

	jest.mock('../formEventEmitter');

	it('should check if preventCancel is being called', () => {
	const dialog = { confirm: jest.fn() };

	// @flow
	import { ConnectionHandler } from 'relay-runtime';
	import { isObject, isArray } from 'lodash/fp';

	export function listRecordRemoveUpdater({ parentId, itemId, parentFieldName, store }) {
	const parentProxy = store.get(parentId);
	const items = parentProxy.getLinkedRecords(parentFieldName);

	parentProxy.setLinkedRecords(items.filter(record => record._dataID !== itemId), parentFieldName);
	}