Matt Broadstone
Matt Broadstone
@danielo515 yes but the problem is that you want `raw` to be true when you fetch the instance, and that's applying it after its already been fetched
@danielo515 hm this might be a little more difficult for you then, as we still use `Instance.setAttributes` rather than `Instance.set`. `setAttributes` doesn't take an `options` object, so you might need...
@danielo515 actually, looking at their code it might be as easy as converting our use of `setAttributes` directly to `set`. Try changing this line: https://github.com/dchester/epilogue/blob/master/lib/Controllers/update.js#L48 to: ``` instance.set(context.attributes, context.options); ```
@H256 looks interesting, if you can put together a PR for the feature I'm sure others in the community will have thoughts on this!
sounds good, looking forward to it!
The pagination options were designed to be defined on a resource level, but you're correct that you might want to control that more finely for what I've termed `subresources` (children/unicorns/whatever...
@jasonhjohnson put together a PR we'll get it in
@jasonhjohnson yeah I think that information is probably better placed directly on the README, I don't think it makes sense to include the polyfill since most browsers already support those...
@coreybutler any chance you could give this a review?
yeah definitely now that we've committed to c++11, smart pointers are of course the way to go :)