Zachary Golba

I agree this would be great. I imagine the API would look something like this: ```javascript import { Controller } from 'lux-framework' class UsersController extends Controller { filter = {...

Also, this is related to #699. @willviles do you have any thoughts regarding this feature?

I believe this is actually an error in the ember-data implementation, not Lux. See [this section](http://jsonapi.org/format/#fetching-includes) of the JSON API spec. I'm going to close this issue for now.

This would be a nice feature to have. Even if it ends up just being docs on how to implement these routes manually.

I agree @dbbk. This is definitely on the radar.

For sure!

@michaelcd there are not any plans for this yet but it is definitely a feature we should have. I'll create a tracking issue for ORM improvements and put a timeline...

Is the intent here to create the answer and the question in the same request or to create an answer for a question that already exists? I can confirm that...

Hmm that's a good point. What would you expect to happen here? A `404` due to the related record not existing? Is that better than just ignoring the invalid resource?...

> First up: great framework! Thanks! > The fixtures are simple module exports which run fine in native v6/v7 and do not need transpiling. This brings up a good point....