chriszhangusc

import React from 'react';
import { getDisplayName } from 'common/utils/hocUtils';

export default function withImageFadeInOnLoad(ImageComponent) {
  class FadeInImage extends React.Component {
    constructor(props) {
      super(props);
      this.state = {
        imageLoaded: false,
      };

chriszhangusc

import React, { Component } from 'react';
import PropTypes from 'prop-types';
import styled from 'styled-components';

const EnhancedImageContainer = styled.div`
  height: 100%;
  width: 100%;
  border-radius: ${props => props.circle && '50%'};
  background-image: ${props => props.fallback && 'linear-gradient(135deg,#846170,#8e8485)'};
  display: inline-block;

chantastic

Hi Nicholas,

I saw you tweet about JSX yesterday. It seemed like the discussion devolved pretty quickly but I wanted to share our experience over the last year. I understand your concerns. I've made similar remarks about JSX. When we started using it Planning Center, I led the charge to write React without it. I don't imagine I'd have much to say that you haven't considered but, if it's helpful, here's a pattern that changed my opinion:

The idea that "React is the V in MVC" is disingenuous. It's a good pitch but, for many of us, it feels like in invitation to repeat our history of coupled views. In practice, React is the V and the C. Dan Abramov describes the division as Smart and Dumb Components. At our office, we call them stateless and container components (view-controllers if we're Flux). The idea is pretty simple: components can't

ghinda

// takes a {} object and returns a FormData object
var objectToFormData = function(obj, form, namespace) {
    
  var fd = form || new FormData();
  var formKey;
  
  for(var property in obj) {
    if(obj.hasOwnProperty(property)) {
      
      if(namespace) {

alexhawkins

'use strict';

/*****************NATIVE forEACH*********************/

Array.prototype.myEach = function(callback) {
    for (var i = 0; i < this.length; i++)
        callback(this[i], i, this);
};

//tests

katychuang

#!/usr/bin/env sh

# first check to see if mongo service is running. you can't delete any files until the service stops so perform a quick check.
launchctl list | grep mongo
  # NOTE: the pipe | symbol means the commands on the right performs on the output from the left
  # grep is a string search utility. `grep mongo` means search for the substring mongo
 
# use the unload command to end the mongo service. this is required to 'unlock' before removing the service.
#    first look for the file to delete
MONGO_SERVICE_FILE=$(ls ~/Library/LaunchAgents/*mongodb*)

lttlrck

git branch -m old_branch new_branch         # Rename branch locally    
git push origin :old_branch                 # Delete the old branch    
git push --set-upstream origin new_branch   # Push the new branch, set local branch to track the new remote

balupton

Node.js Best Practice Exception Handling

Code examples from this stack overflow answer.

zenorocha

Project Name

TODO: Write a project description

Installation

TODO: Describe the installation process

Usage

pksunkara

[user]
	name = Pavan Kumar Sunkara
	email = pavan.sss1991@gmail.com
	username = pksunkara
[init]
	defaultBranch = master
[core]
	editor = nvim
	whitespace = fix,-indent-with-non-tab,trailing-space,cr-at-eol
	pager = delta