Matt Broadstone

@xizhao as you can see [here](https://github.com/dchester/epilogue/issues/34#issuecomment-105891817) it's not complete, but its as complete as it's going to be until someone is inspired to implement the "write" methods for all the...

@AddoSolutions this is partially implemented (all read-related operations) as you can see from the above [comment](https://github.com/dchester/epilogue/issues/34#issuecomment-105891817). If you need support for further operations we can discuss it here, and I...

@danielo515 yes what implementation exists is indeed a part of the main repo and has been released. It's unfortunately undocumented (please let me know if you're interested in doing some...

@cusspvz hey are you going to make that change? I think we can go ahead and merge this then

@sdebionne looks great, would you be willing to include a few tests? (this should mostly be a cut and paste job of existing tests just changing the `autoPopulate` options)

@sdebionne when we auto associate, we create internal "sub-resources". I think what you really are trying to do is conditionally disable the `include` on the sub resources, not _all_ resources....

@sdebionne sorry I've got limited time this week to work on this, I'm confident we can get something working but it will be a few days

@cam861 I believe it was never merged because the tests never passed, and therefore the feature is incomplete. If you want to take a stab at rebasing the PR and...

@kevinsimper it's a legacy holdover from the original implementation, and to this point nobody has really looked into converting it over to be a middleware. Perhaps you'd be interested in...

you should be able to do something like this: ``` resource.create.write.before((req, res, ctx) => { // do something return ctx.skip(); // skip the rest of this milestone }); ```