Chris Grigg

No, it's all work stuff. The gem creates cursor codes based on past queries, so subsequent queries change depending on how you sort initially. On Friday, May 8, 2015, Brian...

Call `unwrapped` in your query chain? (Edited to make this a question so it didn't seem so... stern. ;-) )

@raybooysen I think I'm going to submit them to DefinitelyTyped, instead. I don't want to force TS on the maintainer(s) if they aren't on board with keeping them current.

@tdumitrescu

@tdumitrescu, I've updated this as suggested in your comment. I also added a test to demonstrate that it correctly removes the callback after it is fired. I'm not totally sure...

Just checking in here. Any thoughts?

Thanks for getting back to me. I was thinking about a callback function. The code looks straightforward enough. Any advice on where you'd like to the callback to be stored...

Any chance someone's started working on this? I'm not sure when TypeORM@next will land but it'd be great to have this worked out by then. @buxel we had this discussion...

Aside from a check that the keys are valid, I'm having a bit of trouble finding code and tests that are responsible for those callbacks. @cheerfulstoic were those options removed...

I seem to remember that discussion and decision, but I guess we (I? Probably!) missed the check for valid association options. So, @sandric, the recommended path is to use ActiveRel...