Divya shortdiv

1. Clone your fork:

git clone [email protected]:YOUR-USERNAME/YOUR-FORKED-REPO.git

2. Add remote from original repository in your forked repository:

cd into/cloned/fork-repo
git remote add upstream git://github.com/ORIGINAL-DEV-USERNAME/REPO-YOU-FORKED-FROM.git
git fetch upstream

Locate the section for your github remote in the .git/config file. It looks like this:

[remote "origin"]
	fetch = +refs/heads/*:refs/remotes/origin/*
	url = [email protected]:joyent/node.git

Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this:

Usage:

var player = new Rect(0, 0, 100, 100);
var target = new Rect(50, 50, 100, 100);
player.is = new AABB(player);

player.is.inside(target);
player.is.colliding(target);
player.is.containing(target);

The Ultimate Unit Testing Cheat-sheet

Sinon Chai
Chai
Sinon

How to set up user authentication for a Chrome Extension using the Chrome Identity API

Create a private key file, from which you can create the manifest key and Application ID, as detailed here: https://stackoverflow.com/questions/23873623/obtaining-chrome-extension-id-for-development
Add the manifest key to "key" in manifest.json
Create a new project in Google Developer Console https://console.developers.google.com/project
Go to "APIs & auth > Credentials" and create new client id for a Chrome Application using the Application ID generated in step 3.
Copy the Client ID to oauth2.client_id in the manifest.json

Deprecated?

Stuff I wish I'd known sooner about service workers

I recently had several days of extremely frustrating experiences with service workers. Here are a few things I've since learned which would have made my life much easier but which isn't particularly obvious from most of the blog posts and videos I've seen.

I'll add to this list over time – suggested additions welcome in the comments or via twitter.com/rich_harris.

Use Canary for development instead of Chrome stable

~~Chrome 51 has some pretty wild behaviour related to console.log in service workers. Canary doesn't, and it has a load of really good service worker related stuff in devtools.~~

This content moved here: https://exploringjs.com/impatient-js/ch_arrays.html#quickref-arrays

	ssh-keygen -t rsa -b 4096 -m PEM -f jwtRS256.key
	# Don't add passphrase
	openssl rsa -in jwtRS256.key -pubout -outform PEM -out jwtRS256.key.pub
	cat jwtRS256.key
	cat jwtRS256.key.pub

	<!DOCTYPE html>
	<html>
	<head>
	<title>Test 2 way data binding</title>
	</head>
	<body>
	<div id="app">{{ abc }} - {{ def }} = {{ abc-def }} </div>
	<button id='add'>add</button>
	<button id='double'>double</button>
	<script src='main.js'></script>

	There are many methods for writing Vault policies.

	This gist was created to collect the most common methods
	such that they can be easily used as references for syntax,
	as well as evaluation for which method suits a particular purpose.

	TODO:

	- Add complex policy examples
	- Add @json.file examples