Foreign key being deleted from associated fetch about epilogue

[mark-lester]

So there's two places where this is done, once at the bottom of list.js, but then again, with no attempt at qualification, at the bottom of has-many. I've remarked both out pending thought on how to configure, but do we need both of these ?.

[mbroadst]

@mark-lester hey, it would be helpful if you could link to the code you're referring to in the comments to help me track through this with you. Are you referring to this here? It does indeed look like that is double effort. If you pull it out does it break any tests? I'd say go ahead and remove it otherwise

A little bit of a caveat emptor here: the auto association code was based on an original punt I was working on when I still needed this module for a larger project. It was then completed by another user in collaboration wit me, but it is certainly missing functionality.

As far as the initial question, the primary keys should not be stripped by default, though you may have discovered why they are in your case here already.

[mark-lester]

yes thats the line, I thought it was also going on here https://github.com/dchester/epilogue/blob/master/lib/Controllers/list.js#L141 but I dont have any includes of course, so that wasnt getting called anyway.

[mbroadst]

@mark-lester should be fixed in 8d31e62, would appreciate if you could check that out

[mark-lester]

@mbroadst many thanks indeed, I will test first thing in the morning.

[mark-lester]

yes that worked for me many thanks.