Kurt Ruppel kruppel

2015-01-29 Unofficial Relay FAQ

Compilation of questions and answers about Relay from React.js Conf.

Disclaimer: I work on Relay at Facebook. Relay is a complex system on which we're iterating aggressively. I'll do my best here to provide accurate, useful answers, but the details are subject to change. I may also be wrong. Feedback and additional questions are welcome.

What is Relay?

Relay is a new framework from Facebook that provides data-fetching functionality for React applications. It was announced at React.js Conf (January 2015).

This is a brain dump of my experience trying to get something going with Ember.js. My goal was to get to know the ins and outs of the framework by completing a pretty well defined task that I had lots of domain knowledge about. In this case reproducing a simple Yammer feed. As of this time, I have not been able to complete that task. So this is a subjective rundown of the things I think make it difficult to get a handle on Ember. NOTE: My comments are addressing the Ember team and giving suggestions on what they could do to improve the situation.

App setup

The new guides have pretty good explanation of the various parts of the framework; routers, models, templates, views. But it's not clear how they all get strapped together to make something that works. There are snippets of examples all over the place like:

App.Router.map(function() {
  match('/home').to('home');
});

Read-Only

An important feature for Ember Data is providing helpful error messages when your application tries to do something that is forbidden by the data model.

To that end, we would like for the data model to be able to mark certain records, attributes, and relationships as read-only. This ensures that we can provide errors immediately, and not have to wait for a return trip from the adapter.

This also means that the adapter does not need to handle the case where an application developer inadvertently makes changes to a record that it does not conceptually make sense to modify on the client.

Requirements

The OAuth 2.0 Authorization Framework

This document is intended to be a simplified version of the OAuth 2.0 specification. In particular it has been written with implementors in mind, and as such attempts to trim the spec down to just what you need to implement an OAuth provider or client. It is necessarily not complete, but attempts to introduce spec requirements in the same order in which the protocol proceeds in practise, with everything you need to know about each protocol endpoint brought together in one place rather than scattered across a large document.

	---
	apiVersion: extensions/v1beta1
	kind: DaemonSet
	metadata:
	name: oom-killer
	namespace: kube-system
	labels:
	k8s-app: oom-killer
	spec:
	selector:

	#!/bin/sh

	# Called by "git push" after it has checked the remote status,
	# but before anything has been pushed.
	#
	# If this script exits with a non-zero status nothing will be pushed.
	#
	# Steps to install, from the root directory of your repo...
	# 1. Copy the file into your repo at `.git/hooks/pre-push`
	# 2. Set executable permissions, run `chmod +x .git/hooks/pre-push`

	- Tune /etc/ssh/sshd_config

	UseDNS no # Disable DNS lookups
	GSSAPIAuthentication no # Disable negotation of slow GSSAPI

	don't forget to restart it, use a script provider to set it , or create it with veewee or snapshot it

	- Tune Vagrantfile

	vb.customize ["modifyvm", :id, "--natdnshostresolver1", "on"]

	(function(){

	var key = localStorage.wpt_key;
	if (!key) {
	var prompt = window.__proto__.prompt;
	key = prompt('Your WebPagetest API key, please?');
	if (!key) {
	return gameOver();
	}
	localStorage.wpt_key = key;

	var parser = document.createElement('a');
	parser.href = "http://example.com:3000/pathname/?search=test#hash";

	parser.protocol; // => "http:"
	parser.hostname; // => "example.com"
	parser.port; // => "3000"
	parser.pathname; // => "/pathname/"
	parser.search; // => "?search=test"
	parser.hash; // => "#hash"
	parser.host; // => "example.com:3000"