Philip Roberts

This is not just a windows issue, fairly sure this affects all platforms (certainly keeps breaking for me on osx now that I'm using node 4).

Yeah, you're right, I was trying to run it in an es6 environment (node 4) and use Babel + this to just compile the async/await stuff rather than everything down...

No worries, yeah to be honest it sounds like just mentioning in the docs that you need es2015 set for this to work is probably the best solution. > Why...

Hey @flipside, thanks for submitting this! I think I'm heading towards +1 on this idea. I've a couple of thoughts though - forgive me if I'm being slow. First up:...

Hey @jackboberg! Yeah, that doesn't look correct, good spot. It's sort of related to this https://github.com/AmpersandJS/ampersand-state/issues/92 too. The reason this is happening is: when we initialize a parent model we:...

@jackboberg it's legacy from backbone. They had some discussion about adding that behaviour but it never got merged: https://github.com/jashkenas/backbone/pull/2636/files. On potential challenge I can see of adding it, is that...

Hey @TimBeyer! There's a lot here, that I'm trying to get my head around, so bear with me if I'm misunderstanding you. > sync aka ampersand-sync is accessed from the...

> Regarding using ajaxConfig on a BaseModel: Oh, sorry, I missed the point about being on the server. > Basically what's really in the way is Model.prototype.sync, which directly delegates...

@kirisu can you outline a bit more specifically the issues you're running into (i.e. what you're trying to do?). This is part bug/part by intention, but it's behaviour we're mid...

> The only issue I can think of is change listeners - any ideas on this? Should we be checking for the presence of a change or change:${derivedKey} listener, then...