Julien Nakache

Hello Nick, We are actually also exploring building a tight integration between GRPC and GraphQL at my company. We are still very early in the process and we won't get...

Great thanks. The current approach does make sense a lot of sense now. The aliasing spec of GraphQL is indeed going to require request-specific proto generation. That's a little unfortunate...

One more thought. One of the use cases we were hoping to support is to have one canonical GraphQL schema aggregating / stitching multiple downstream GraphQL servers via GRPC so...

+1 with this. As of v2, we no longer have the ability to extend / wrap the graphql query execution. Middelwares alone are not sufficient to workaround this because they...

FYI I reverted to https://github.com/prisma/graphql-prisma-typescript/commit/2d4994cec0b5c0b4f3c5ff1d0372dd0e1cea166f and it seems to work fine. I had to use `npm install` thought because `yarn` was failing: ``` error An unexpected error occurred: "https://registry.yarnpkg.com/flatmap-stream/-/flatmap-stream-0.1.2.tgz: Request...

Just a heads that there is a PR currently opened that addresses the N+1 problem. Would love to get your input. Cheers. See https://github.com/graphql-python/graphene-sqlalchemy/pull/253#pullrequestreview-309278130

Yes that's available as of [`2.3.0`](https://github.com/graphql-python/graphene-sqlalchemy/releases/tag/2.3.0). See release notes how to enable it. Would love feedback on performance and usability.

Hi everyone, I'm interesting in pushing this over the finish line. We all agree here that the conversion should be consistent. The only thing left to decide is wether we...

Please provide an example of what the API would look like.

@thejcannon I think it's definitely an interesting route to explore. I have 2 main concerns with that approach: 1. It may prevent each library from building on the strengths or...