Intro to React | Upcase

On this weeks episode Chris presents an introduction to Facebook's React.js framework. React is a JavaScript framework used for building dynamic UIs. Learn why React is interesting and what makes it different from the other frameworks for JS UIs. ...
This is a companion discussion topic for the original entry at
1 Like

Thanks, that was a great introduction.

1 Like

Very cool, I’ve been playing react for a few weeks and enjoying it more than angular’s directives.

This is a decent tutorial for getting it up and running within rails. I haven’t looked at testing react components at all yet, anyone have experience there or resources?

The other very cool idea with react is flux.

1 Like

I found that using Flux helped avoid having to use a top-level component that was effectively storing global state and then passing it down to grandchildren or great-grandchildren components. If you are passing props through more than one level of component to get them somewhere else (you have more than one component receiving the prop and passing it on without using it in rendering), that’s a code smell.

ReactDC did a comprehensive review of Flux implementations recently. I’m curious about giving more of them a try. We’re using Marty.js at Cortex, and I’ve had a great experience with it. It’s under active development, has reasonable documentation, and the author is responsive to bug reports and suggestions.

Anyone else find it extremely easy to follow along with Chris’s videos?


very interesting indeed. I wonder if React.js is a replacement for Ember.js, or if both frameworks serve another purpose.



Excellent overview! Just what I needed. Are there any plans for a React trail? I’d love to see something on Vanilla React, Flux, Reflux, and React Native.

1 Like

@imwithsam Thanks! We’ve started using React on more client apps and as our expertise grows I could see us producing more content. At a minimum I have a strong interest in React so I will likely end up doing a few more Weekly Iterations on it.


I’m definitely interested in a React Trail with react-rails, reflux and react-router. There is so much churn around Javascript right now. I’m having a difficult time deciding on ES6, webpack or plain rails assets, etc.

I think it would be great to do a Rails/React trail.

I’ve found Chris to be the best presenter on Upcase I’ve seen so far! You should do more videos :slight_smile:

At 10:58, should it it be this.props.users rather than this.state.users, since we are not setting state anywhere rather than just passing props?

I’m actually going to take a gamble on React and learn it for a new client’s app. I would love to see how Thoughtbot approaches React! I would love a new Trail with React/Rails!


Me :relaxed:

Really looking forward to more in-depth videos on React

I’d be really interested in more videos around React. React+Rails maybe.

I would also love to see more React related videos/trial.
Been trying to get my head around React + Flux + Rails with not much luck. So I would find Flux/Rails explanations very useful.

React would be my top pick for a new trail. Everything I can find on the web only goes so far as to give a “Hello World” level example when dealing with Rails. There is far too much that happens in the middle when building out a real application.

I would love to see the process of implementing React on a simple Rails crud app (preferably via React-Rails).


I’m with you on this idea. I love React and using Rails API gem to build isomorphic apps

1 Like

Great intro to ReactJS @christoomey !

I’m starting to dabble with it by using the react-rails gem and have a few questions:

  1. When using ReactJS components, is there a way that we can use Rails helpers (like link_to) within JSX?
  2. Similar to first question, Is it possible to use simple_form within components? I’m building all of my markup manually right now :frowning: .
  3. How do we deal with ruby logic within a component? For example, what if you need to call a boolean ruby method on an object in a collection that is passed in as a prop. (i.e. this.props.article.printed?).
  4. How would you recommend breaking down your react components into separate files? Some find it a bit painstaking to have to navigate over several partials when working with something they consider a single component (like a table for instance)?
  5. Do you know of any vim plugins that allow the use of gf on react component names?

Cheers! :beers:

1 Like