- Fix error parsing
- Add missing
yieldin theloginfunction
| # macports | |
| export PATH="/opt/local/bin:/opt/local/sbin:$PATH" | |
| # PHP | |
| export PATH="/usr/local/php5/bin:$PATH" | |
| # mysql | |
| export PATH="/usr/local/mysql/bin/:$PATH" | |
| # composer | |
| export PATH="$HOME/.composer/vendor/bin:$PATH" | |
| # npm | |
| export PATH="./node_modules/.bin:$PATH" |
| { | |
| "name": "polymer-globals-behavior", | |
| "dependencies": { | |
| "polymer": "Polymer/polymer#~1.0.5" | |
| } | |
| } |
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
| // | |
| // Implementation using express-jwt middle | |
| // | |
| var express = require('express'), | |
| ejwt = require('express-jwt'), | |
| jwt = require('jsonwebtoken'), | |
| passport = require('passport'), | |
| bodyParser = require('body-parser'), | |
| LocalStrategy = require('passport-local').Strategy, | |
| BearerStrategy = require('passport-http-bearer').Strategy; |
| [self.apiClient retrieveConnectedServicesWithSuccessBlock:^(NSDictionary *services) { | |
| NSArray *facebookTokens = services[@"facebook"]; | |
| if (facebookTokens.count == 0) { | |
| return; | |
| } | |
| NSDictionary *mostRecentFacebookTokenDict = facebookTokens[0]; | |
| NSNumber *refreshTimeNumber = mostRecentFacebookTokenDict[@"refreshTime"]; | |
| NSDate *refreshDate = [NSDate dateWithTimeIntervalSince1970:[refreshTimeNumber doubleValue]]; |
When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:
const Article = require('../../../../app/models/article');Those suck for maintenance and they're ugly.
| function extend(base) { | |
| var parts = Array.prototype.slice.call(arguments, 1); | |
| parts.forEach(function (p) { | |
| if (p && typeof (p) === 'object') { | |
| for (var k in p) { | |
| if (p.hasOwnProperty(k)) { | |
| base[k] = p[k]; | |
| } | |
| } | |
| } |