start new:
tmux
start new with session name:
tmux new -s myname
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
| =Navigating= | |
| visit('/projects') | |
| visit(post_comments_path(post)) | |
| =Clicking links and buttons= | |
| click_link('id-of-link') | |
| click_link('Link Text') | |
| click_button('Save') | |
| click('Link Text') # Click either a link or a button | |
| click('Button Value') |
As configured in my dotfiles.
start new:
tmux
start new with session name:
| import { Component } from "React"; | |
| export var Enhance = ComposedComponent => class extends Component { | |
| constructor() { | |
| this.state = { data: null }; | |
| } | |
| componentDidMount() { | |
| this.setState({ data: 'Hello' }); | |
| } | |
| render() { |
| /** | |
| * ReactJS: JavaScript like you've always done it. | |
| * | |
| * This example renders your top ten most followed friends/followers, `filter`ing | |
| * only your favorites, and putting a star on all verified accounts. | |
| * | |
| * With ReactJS, any time your data changes, the UI is always brought up to date | |
| * automatically. If friends length changes, or followCount - it always shows what | |
| * `render` describes. | |
| */ |
| #Model | |
| @user.should have(1).error_on(:username) # Checks whether there is an error in username | |
| @user.errors[:username].should include("can't be blank") # check for the error message | |
| #Rendering | |
| response.should render_template(:index) | |
| #Redirecting | |
| response.should redirect_to(movies_path) |
This article has been given a more permanent home on my blog. Also, since it was first written, the development of the Promises/A+ specification has made the original emphasis on Promises/A seem somewhat outdated.
Promises are a software abstraction that makes working with asynchronous operations much more pleasant. In the most basic definition, your code will move from continuation-passing style:
getTweetsFor("domenic", function (err, results) {
// the rest of your code goes here.NOTE I now use the conventions detailed in the SUIT framework
Used to provide structural templates.
Pattern
t-template-name