| # Version key/value should be on his own line | |
| PACKAGE_VERSION=$(cat package.json \ | |
| | grep version \ | |
| | head -1 \ | |
| | awk -F: '{ print $2 }' \ | |
| | sed 's/[",]//g') | |
| echo $PACKAGE_VERSION |
| /* jshint esnext:true */ | |
| 'use strict'; | |
| import React from 'react'; | |
| import Header from './header'; | |
| import Workspace from './workspace'; | |
| import Footer from './footer'; | |
| // Manually call upgradeElement / MaterialLayout on the main layout div *AFTER* its been rendered in the DOM. | |
| export default React.createClass({ |
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:
| #!/bin/sh | |
| git rev-parse 2>/dev/null | |
| if [[ $? != 0 ]] | |
| then | |
| echo "Not a git repo" | |
| return | |
| fi |
| (ns user) | |
| (def app | |
| "Intenal Helper" | |
| (fnil conj [])) | |
| (defprotocol PathSeq | |
| (path-seq* [form path] "Helper for path-seq")) | |
| (extend-protocol PathSeq |
A curated list by Eric Elliott and friends. Suggest links in the comments below.
This is a very exclusive collection of only must-have JavaScript links. I'm only listing my favorite links. Nothing else makes the cut. Feel free to suggest links if you think they're good enough to make this list. The really curious should feel free to browse the comments to find other links. I can't guarantee the quality of links in the comments.
Some of these links are affiliate links, meaning that if you make a purchase, I might earn a little money. This has absolutely no bearing on whether or not links make the list. None, whatsoever. However, it does allow me more resources to fight poverty with code. Every little bit counts.
http://stackoverflow.com/questions/310813/how-do-you-perform-code-reviews
How are code reviews performed on your development team?
I've been a developer for several years now in several different companies and I have noticed that there isn't a consistent approach to performing code reviews.
At my current company, code reviews are non-existent, which has led to a significant decrease in the quality of the code. At previous jobs, code reviews ranged from just making sure coding standards were enforced to nazi-like line by line reviews that took days to complete.
So I'm wondering what its like for everyone else out there. And in particular, what tools do you use to perform the reviews? And do you find that code reviews help rather than add to the length of time needed for a given project?
I hereby claim:
To claim this, I am signing this object:
| ;; Updated tutorial code for Om 0.1.6, 2014-01-16 | |
| ;; http://www.lexicallyscoped.com/2013/12/25/slice-of-reactjs-and-cljs.html | |
| ;; See comments below for details on the changes. | |
| (def app-state | |
| (atom {:comments [{:author "Pete Hunt" :text "This is a comment."} | |
| {:author "Jordan Walke" :text "This is *another* coment"}]})) | |
| (defn comment [{:keys [author text]} owner] | |
| (om/component |
| <html> | |
| <body> | |
| <script src='//ajax.googleapis.com/ajax/libs/jquery/1.10.1/jquery.min.js'></script> | |
| <script src='//cdnjs.cloudflare.com/ajax/libs/underscore.js/1.4.4/underscore-min.js'></script> | |
| <script src='//cdnjs.cloudflare.com/ajax/libs/underscore.string/2.3.0/underscore.string.min.js'></script> | |
| <script src='//cdnjs.cloudflare.com/ajax/libs/coffee-script/1.6.3/coffee-script.min.js'></script> | |
| <script src='//cdnjs.cloudflare.com/ajax/libs/reactive-coffee/0.0.5/reactive-coffee.min.js'></script> | |
| <script type="text/coffeescript"> | |
| bind = rx.bind | |
| rxt.importTags() |