Gschorkopf/course_show

@sebastiangeiger / @ChaeOkay / @killpack / @pdougall1 

Anyone mind giving this a gander?
Mmm.... semantically, a `show` isn't a resource, so I think it's sorta confusing to have `this.resource('show')`.

I guess I don't see any advantage in doing it this way, @pdougall1 . In general, for frameworks that rely heavily on convention over configuration (like Rails and Ember), you need to have a really good reason for wanting to do something unconventionally. What's the reason here? 

If the reason is to more tightly couple this route to the Rails route, I think that's a bad idea. You should treat the API like a black box: who's to say what the name of that controller action is? And why does it matter here? 

Here's another thought: what's the difference between getting a course and showing a course? I don't think there is one. So I don't think there's any advantage in distinguishing between `CourseRoute` and `CoursesShowRoute`. I don't think this change is buying us anything we don't already have.