attachConnectorsToContext undefined about graphql-tools

[helfer]

@mimamuh Thanks for reporting this, I did indeed forget to export them. I will fix it with the next PR.

You're right, these two definitions are not exactly the same. We're still working on the details for connectors, and it has even evolved a bit since then. I'm currently working on PR #46 that has a bit more specifics, but is still not quite final. Would be great if you could give that a read and tell me if it makes sense!

Once we have something more stable, the docs should be updated.

[mimamuh]

Hi, yeah, it makes sense at first glance. I like your ideas!

If I understood it properly, the connectors would cache and maybe batch my calls to the db automatically per graphql-query? It would be awesome. And the models are there to manage different connector per query when needed. Would things like permission handling be part of models or the resolve functions then?

[helfer]

Yes, connectors would cache per query and batch (per tick on Node). They could also be made to cache for longer, of course, that should be easy.

Permissions should be handled in models, or in some cases resolvers (not 100% sure yet). I'm thinking that decorators will be very interesting for permissions.