gcatlin

brew update
brew versions FORMULA
cd `brew --prefix`
git checkout HASH Library/Formula/FORMULA.rb  # use output of "brew versions"
brew install FORMULA
brew switch FORMULA VERSION
git checkout -- Library/Formula/FORMULA.rb    # reset formula

## Example: Using Subversion 1.6.17
#

stephensauceda

/* 
 *    Steps
 * 1. Rename your gulpfile.js to gulpfile.babel.js
 * 2. Add babel to your package.json (npm install -D babel)
 * 3. Start writing ES6 in your gulpfile!
 */
 
 import gulp from 'gulp'; // ES6 imports!
 import sass from 'gulp-sass';
 

3runoDesign

web: sh app_boot.sh
worker: php artisan queue:listen

coolaj86

Please petition Github to support HTTPS on github pages: https://github.com/contact

Here's what I wrote:

Obviously, a lot of people want HTTPS for github pages:

• isaacs/github#156

Until recently, that would be difficult to implement but, as it turns out, the implementation is pretty much complete:

• https://letsencrypt.org >* https://github.com/letsencrypt/lets-encrypt-preview

JeffreyWay

<?php


class PhotoApiTest extends TestCase {
    
    public function setUp()
    {
        parent::setUp();

        Route::enableFilters();

jerbob92

<?php

/**
 * @file
 * Contains \Drupal\mymodule\Menu\MyModuleMenuLink.
 */

namespace Drupal\mymodule\Plugin\Menu;

use Drupal\Core\Plugin\ContainerFactoryPluginInterface;

heat

beforeEach(function() {
	this.addMatchers({
	    toBeInstanceOf: function(expectedInstance) {
	    	var actual = this.actual;
	    	var notText = this.isNot ? " not" : "";
	    	this.message = function() {
	    		return "Expected " + actual.constructor.name + notText + " is instance of " + expectedInstance.name;
	    	};
	    	return actual instanceof expectedInstance;
	    }		

varunachar

// Root is hotel

{
  status : "ok",
  statusCode : 200,
  hotels : [{
    name : "Taj Palace",
    location : {
      lat : 12
      lng : 77

alexpott

<?php

/**
 * @file
 * Install, update and uninstall functions for my project.
 */

/**
 * Implements hook_install().
 *

DavidFrahm

/*
 * If we assume that the philosophy of a provider is only configuration then it makes more sense in most
 *     cases to test that "it" is configured. As the "it" in this case is the resulting service, using
 *     module to do the configuration and then inject to test that the configuration worked seems to make sense.
 * The trick to understanding these tests is to realize that the function passed to module() does not get called until inject() does it's thing. So assigning to a closure variable in the module initialization function ensures that the Provider is defined before control passes to the injected function. Then you're free to interact with the Provider's configuration interface. The technique is a little bit broken in that the Provider has already provided it's Service. But, if you can tolerate that limitation it works.
 * 
 * Most of this I learned from https://github.com/angular/angular.js/issues/2274
 *
 * There are multiple describe() suites and it() tests, just to help us trace what's going