Matt Broadstone

@H256 I think theoretically we could switch to `_.defaults` there, in order to not overwrite any existing values in `context.attributes` that aren't null/undefined. This would be more in line with...

@cusspvz sounds like a good idea, patches are very welcome! It would be nice not to depend on that kind of trickery anymore :)

I feel a bit uncomfortable adding that kind of feature to epilogue because I think it could be considered quite dangerous (you're basically providing a way for someone to remotely...

@mark-lester ah, I thought you meant providing a top level describe method (iterating all available models and therefore giving a map of what's available). I'm not actually against providing this...

@sdebionne that sounds reasonable.

@AddoSolutions sorry I seem to have missed that PR, that does pretty much look like what he's asking for here. I prefer the term `autoPopulate`, as well as defaulting to...

@sdebionne sounds reasonable, although I'd prefer if we kept it semantically related to the controllers (rather than the endpoints which can be arbitrary): ``` js associations: { autoPopulate: { read:...

@sdebionne `include` is used to include other Sequelize models in your search, see [here](https://sequelize.readthedocs.org/en/latest/docs/querying/#relations-associations) for examples. In this case it seems to be enough that you do what @AddoSolutions did...

@sdebionne no autoPopulate and autoInclude are separate concepts here. Here's a breakdown of the current state: - if you don't want to automatically include all related models, simple do not...

@sdebionne `include` is a concept related to a Sequelize query: "This model will be _included_ in the query". `populate` is an epilogue concept, such that epilogue will figure out which...