Pekka Heikura

This is the entry point https://github.com/aws/aws-lambda-dotnet/blob/master/Libraries/src/Amazon.Lambda.RuntimeSupport/lambda-entrypoint.sh. If `LAMBDA_DOTNET_MAIN_ASSEMBLY` not set then it seems to pick the first one.

Multiple servers would be tricky to implement. Subscriptions itself would work but how would you get the transport to work? Especially when 99% time client is browser connecting trough web...

Any update on this? Causing major headache in government projects where Soap is the new thing.

As an workaround we use AutoMapper to map between the same types in different namespaces. Our mapping profile automatically creates maps between same named types in given namespaces. This works...

There are multiple C# dataloader implementations already so I don't think I want to make another

Modifications are supported by using the extension methods starting with `With{Property}`

Add external asset support to tanka-docs-gen first

Note that this is not a fork and was started from scratch because I wanted something simple without legacy pressure. First it was just a experiment to understand the graphql...

To see the differences in action go to https://github.com/pekkah/tanka-graphql-samples * schema stitching/splitting /manipulation * jwt based authentication Etc.

One new feature coming up in 2.0.0 is a new parser using Span which improves the performance by both being faster and allocating less. It's compatible with current GraphQL draft...