Furqanameen

1. Initially install your pry-rails to group development on your apps Gemfile

group :development do
  # ..
  gem 'pry-rails'
  # ..
end

kolodny

export const doTheThing = () => (dispatch, getState) => {
  const users = getState();
  dispatch({
    type: 'THE_THING',
    users,
  });
};

xjamundx

This is the follow up to a post I wrote recently called From Require.js to Webpack - Party 1 (the why) which was published in my personal blog.

In that post I talked about 3 main reasons for moving from require.js to webpack:

1. Common JS support
2. NPM support
3. a healthy loader/plugin ecosystem.

Here I'll instead talk about some of the technical challenges that we faced during the migration. Despite the clear benefits in developer experience (DX) the setup was fairly difficult and I'd like to cover some of the challanges we faced to make the transition a bit easier.

rceee

#This is how I set up my Rails 3 User model to have a pretty URL/ID "slug" without adding a slug field to the database

Wilto

Adaptive Image Element

Author:

Mat Marquis

Status of this Document

This is an unofficial draft spec, not formally endorsed by the WHATWG. It is suitable only for reviewing the details of the proposed element.

Table of Contents

jbgo

UPDATE: A better way! (August 2015)

As pointed out by @johntyree in the comments, using git reflog is easier and more reliable. Thanks for the suggestion!

 $ git reflog
1ed7510 HEAD@{1}: checkout: moving from develop to 1ed7510
3970d09 HEAD@{2}: checkout: moving from b-fix-build to develop
1ed7510 HEAD@{3}: commit: got everything working the way I want
70b3696 HEAD@{4}: commit: upgrade rails, do some refactoring

rstacruz

Rails Models

Generating models

$ rails g model User

Associations

belongs_to

has_one