trotzig

describe('Button', () => {
  beforeEach(() => {
    this.subject = () => {
      return React.addons.TestUtils.renderIntoDocument(
        <Button {...this.props} />  
      );
    };
  });
  
  describe('with a `text` prop', => {

trotzig

describe('Button', () => {
  describe('with a `text` prop', => {
    it('renders the text', () => {
      var button = React.addons.TestUtils.renderIntoDocument(
        <Button text="Click me" />  
      );
      expect(button).toHaveText('Click me');
    });
    
    describe('and an `icon` prop', () => {

trotzig

describe('Button', () => {
  subject(() => {
    return React.addons.TestUtils.renderIntoDocument(
      <Button {...this.lets['props']} />  
    );
  });
  
  describe('with a `text` prop', => {
    let('props', { text: 'Click me'});
    

trotzig

aliases:
  '$' => 'third-party-libs/jquery'
  '_' => 'third-party-libs/underscore'

trotzig

lookup_paths:
  - 'app/assets/javascripts'
  - 'vendor/bower_components'

trotzig

var $ = require('jquery');
var resolveDOMNode = require('support/resolve_dom_node');

/**
 * This file adds a `toHaveText` matcher to our Jasmine spec. To use it, do
 * something like:
 *
 *   expect(component).toHaveText('Support John');
 */
beforeEach(function() {

trotzig

/**
 * Convenience method to resolve a component or a DOM node to a DOM node. If the
 * passed in `node` is a React component, the root DOM node of the component is
 * returned. If `node` is already a DOM node, that node is returned in itself.
 *
 * @param {Object} node A React component or a DOM node
 * @return {?Object} a DOM node
 */
var resolveDOMNode = (node) => {
  if (!node) {

trotzig

$z-index-menu: 100;
$z-index-navigation-main: 200;
$z-index-floating-action-button: 300;
$z-index-modal-wrapper: 400;
$z-index-toast: 500;
$z-index-n-progress: 600;

trotzig

#!/bin/bash

# Run the script like this:
# > bash count_commits.sh <name>
# where name is a uniquely identifying string for a contributor, e.g. "Lencioni"

repos=( "causes" "brigade" "devscripts" "cuisine" "scss-lint"
"brigade-cap-tasks" "overcommit" "mock_redis" "sass-enhance"
"eslint-config-brigade" "react-waypoint" "haml-lint" "async_observer" "bender"
"react-simple-pie-chart" "tech-interview" "url-sweatshirt" "db-query-matchers"

trotzig

Diffux CI lightning talk proposal

Talk title: Visual diffing for React components

Are you worried that your CSS changes will break the styling of a component?
Are you scared that your code refactoring will result in visual bugs? Do you
find it difficult to understand how a code change affects the appearance of your
components? If you answer yes to any of the questions above, you want a visual
diffing tool. While many exist, Diffux-CI is the best one for React.