Anselm Christophersen anselmdk

jsconfig.json

{
  "compilerOptions": {
    "baseUrl": "./src",
    "target": "ES6",
    "jsx": "preserve",
    "allowSyntheticDefaultImports": true
  },
 "exclude": ["build", "node_modules"]

Go to File -> Settings -> Tools -> Terminal and change Shell path based on the the installed git version.

for 64bit:

"C:\Program Files\Git\bin\sh.exe" --login -i

for 32bit:

"C:\Program Files (x86)\Git\bin\sh.exe" --login -i

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.

JSX Spread Attributes

If you know all the properties that you want to place on a component a head of time, it is easy to use JSX:

  var component = <Component foo={x} bar={y} />;

Mutating Props is Bad, mkay

	#!/bin/bash

	# Following the guide found at this page
	# http://programmingarehard.com/2014/03/17/behat-and-selenium-in-vagrant.html

	echo "\r\nUpdating system ...\r\n"
	sudo apt-get update


	# Create folder to place selenium in

	<?php
	/**
	* Creates a Flat table view for a given class
	* @author Mark Guinn <[email protected]>
	* @date 06.13.2014
	*/
	class CreateViewForClass extends BuildTask
	{
	protected $title = 'DEV: Flat View for Class';
	protected $description = 'Use class=XXXX to create a flat view of all the tables that make up a given class';

	#!/bin/sh

	# This is a skeleton of a bash daemon. To use for yourself, just set the
	# daemonName variable and then enter in the commands to run in the doCommands
	# function. Modify the variables just below to fit your preference.

	daemonName="DAEMON-NAME"

	pidDir="."
	pidFile="$pidDir/$daemonName.pid"

	HtmlEditorConfig::get('cms')->setOptions(array(
	"skin" => "default",
	"style_formats" => array(
	array(
	"title" => "Lead",
	"selector" => "p",
	"classes" => "lead"
	),
	array(
	"title" => "Subheader",

	#!/bin/bash
	#
	# ss-upgrader.sh
	#
	# INTRODUCTION
	#
	# There are some threads on the SS forums that describe the techdocs for upgrading a 2.4 site to 3.x as being too technical. Mainly from content authors who
	# also happen to be site maintainers - they are not coders.
	# The aim of this script is to therefore to automate - in as much as this is possible in a user-configured, open-source software project - to help those new to
	# SS3 upgrade from 2.x as smoothly as possible.