Marc Schipperheyn

The root cause of all these issues is the requirement of recursive imports. This PR (https://github.com/RobinBuschmann/sequelize-typescript/pull/1206) solve that in part. But in order to completely solve this, I think the...

> There's really no way around it, that's why they're using arrow functions to defer the model resolution in associations. As long as you don't start importing other unnecessary stuff...

IMHO the code below should be adjusted to help avoid the need for recursive imports: ``` private associateModels(models: ModelCtor[]): void { models.forEach((model) => { const associations = getAssociations(model.prototype); if (!associations)...

@RobinBuschmann I took an initial stab at this. Would be great if someone could give me some feedback on whether this is a good idea or not: https://github.com/mschipperheyn/sequelize-typescript/commit/89bbef67201394d2fe4d832a8e2e8c4565e67bb7

I've added a PR though. It does solve circular depencencies as being thrown by the webpack CircularDependencyPlugin https://github.com/RobinBuschmann/sequelize-typescript/pull/1206

I have the same problem. session null or destroy solutions seems a bit ham fisted. If you just want to log out and keep other session variables, this doesn't work....

Just logged a similar issue on express

I tried using the RNFetchBlob whatwg-fetch polyfill in the hope that the request would show up in Network debugging. However, the opposite happens. If you use whatwg-fetch through RNFetchBlob, network...

my renderRow method doesn't use sectionId. I'll investigate if this could be the issue. Also, I resort data when new data comes in load-more style. Wonder if this screws with...

In many case state should be replaced by props anyways. I wonder if supporting this case, is worth it and if the same effect cannot be achieve by developers rewriting...