i-tu

  componentWillReceiveProps(nextProps) {
    if (nextProps.lastRequestedUserLocationAt > this.props.lastRequestedUserLocationAt) {
      this.centerMapToUser(nextProps.currentLocation);
    }

    if (nextProps.lastUpdated > this.props.lastUpdated) {
      const markers = this.createMarkersForLocations(nextProps);

      if (markers && Object.keys(markers)) {
        const clusters = {};

vasco3

Table of Contents generated with DocToc

• FrontEnd Masters - ES6 notes
  • Proper Tail Call (PTC)
  • Function Hoisting
  • Variables
    • Temporal Dead Zone
• Rest Parameters

tsiege

ANNOUNCEMENT

I have moved this over to the Tech Interview Cheat Sheet Repo and has been expanded and even has code challenges you can run and practice against!






\

traviskaufman

Better Jasmine Tests With this

On the Refinery29 Mobile Web Team, codenamed "Bicycle", all of our unit tests are written using Jasmine, an awesome BDD library written by Pivotal Labs. We recently switched how we set up data for tests from declaring and assigning to closures, to assigning properties to each test case's this object, and we've seen some awesome benefits from doing such.

The old way

Up until recently, a typical unit test for us looked something like this:

describe('views.Card', function() {

ErikHellman

public class PaintView extends View {
    public static final int MAX_FINGERS = 5;
    private Path[] mFingerPaths = new Path[MAX_FINGERS];
    private Paint mFingerPaint;
    private ArrayList<Path> mCompletedPaths;
    private RectF mPathBounds = new RectF();

    public PaintView(Context context) {
        super(context);
    }

kgates-github

var numTiers = 100,
    triangle, 
    start, 
    stop;

/**
*
* First version uses recursion
*
*/