add ability to pass in "include" to context for relational mapping in list results about epilogue

[dchester]

The implementation of this from your fork is merged in with v0.3.0. Thanks!

[bradisbell]

This would be a great feature. Did it ever land in a release? The comment from last March seems to indicate it did, but I don't see anything in the readme, and the example from @mbroadst doesn't do anything. I'm using v0.3.2 from NPM.

[mbroadst]

@bradisbell yes this feature was merged in and will work, but is generally supported by passing it in to the resource definition like so:

var userResource = epilouge.resource({
    model: models.User,
    include: [models.Address],
    endpoints: ['/rest/users', '/rest/users/:id']
});

This include basically aliases to sequelize's include, so you can do stuff like:

include: [models.Address, { model: models.Person, as: 'peeps' }]

and all that jazz. My intention, based on the last issue brought up, is to provide this for legacy use but to add a feature to opt into "auto-association", pulling in all related associations and potentially new endpoints (like "user/:id/address/:id" for instance). This is not going to make it in in the next two weeks though 😄

The documentation needs a serious update (as you've probably noticed from other closed issues here there are at -least- two other undocumented features: 'sort' and 'q' query items), if you're interested changes would be gladly accepted. Aside from that, I'm out of the country for the next 10 days, so it'll be a little before I can properly update the documentation. In the meantime, the tests have pretty good coverage of the features provided, and show you how you can use them.

[bradisbell]

I would be happy to contribute to this great project, but I'm just now getting my feet wet with Sequelize and epilogue so I will wait until I know what I'm doing. I'll check out the tests, thanks! Enjoy your trip!