We'll recap everything we've learned so far, so it's fresh in our minds.

There are several types of repetitive routes that most apps end up needing for the following purposes

• Creating a new record
• Updating an existing record
• Showing a record
• Showing a list of records

We'll devise a common abstraction for each of these, and DRY up our code by establishing some conventions within our project.

Let's DRY up our routes for showing a list of records, and the route for creating a new record, by building some general purpose mixins.

You're no doubt aware of new language features coming to the JavaScript world, but since some of us have years of experience writing ES5 code, it's hard to develop new habits that take advantage of the new stuff.

We'll look at some ideal places to apply destructured assignment, enhanced object literals, ES6 classes, async/await and more, with a specific focus on how the new ideas mix well with Ember.

• Rewrite our logout logic using async/await
• Write an acceptance test for visiting a record and comment on it, using async/await

ember-cp-validations takes an approach to validating ember-data records (or really, any Ember.Object subclass) that's built entirely using computed properties. We'll look at how to apply this library, customize error messages, display them on the screen, and even integrate with ember-data to surface server-side errors in the UI.

Implement clients-side validation for comments, where anonymous comments must be less than 140 characters, but non-anonymous comments can be up to 255.

Break for Lunch