Allow recursive connections with DjangoFilterConnectionField

[tangerilli]

You can't currently create a DjangoFilterConnectionField connection that references its containing node type, because the __init__ method didn't expect the type to be a callable, and even if it did, the callable couldn't return anything at that time, because the type wouldn't be defined yet. These changes move anything that's dependent on the type into properties, so as to defer access until after class initialization.

[coveralls]

Coverage increased (+0.2%) to 92.553% when pulling 207f4eb on tangerilli:recursive-nodes into d8567f1 on graphql-python:master.

[nickhudkins]

@syrusakbary I have submitted a PR to @tangerilli's fork in hopes of avoiding opening another PR here, but hopefully if he accepts, we can get this conflict resolved and merged!

[coveralls]

Coverage increased (+0.2%) to 92.615% when pulling e77962b on tangerilli:recursive-nodes into 4246cea on graphql-python:master.

[coveralls]

Coverage increased (+0.1%) to 92.566% when pulling 9b1c1b4 on tangerilli:recursive-nodes into 4246cea on graphql-python:master.

[coveralls]

Coverage increased (+0.2%) to 92.659% when pulling e82ee88 on tangerilli:recursive-nodes into 4246cea on graphql-python:master.

[austinnichols101]

Is there any workaround for this issue, or plans to update/integrate this PR?

I'm running into this problem all over the place....

[tangerilli]

@austinnichols101 I've resolved the conflicts here

@syrusakbary is there anything you'd like to see changed here in order to get this merged?

[austinnichols101]

Thanks @tangerilli !