This week we took a pretty deep look at the methods available in Routes and Components. Next week we are going to build an app using some of this knowledge so we can see everything all work together. Today let's do a little exercise. As we discussed, components are short lived, they don't hold state after being destroyed. Let's create an app that has a component that:

  • displays a value
  • has an input helper that allows a user to change the value
  • maintains the value when the user navigates away from the route with the component


EmberConf 2016: MiniTalk: Accessibility in Ember by Ben Holmes

Component dependency injection in Ember.js by Lauren Tan

Building a performant real-time web app with Ember Fastboot and Phoenix by Mike North

Building Ambitious Web Applications with Ember.js by Daniel Gynn