Differences From graphql-dotnet/server about tanka-graphql

[joemcbride]

Writing the schema in .gql files seems to be the way the community has gone down and actually recommends. Unfortunately, graphql-dotnet doesn't seem to have that support.

It does, it was added in 2.0. See “Schema First Approach” in the introduction. https://graphql-dotnet.github.io/docs/getting-started/introduction

[RehanSaeed]

Oh and finally, what features are missing as compared to graphql-dotnet/server but also apollo server.

[pekkah]

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 spec more closely but quickly became whole project of its own. It's not meant to compete with graphql-dotnet. I'm also trying to keep it more as an library instead of offering everything out of the box. I make no guarantees on backwards compatibility at least until version 1.0.

[RehanSaeed]

Writing the schema in .gql files seems to be the way the community has gone down and actually recommends. Unfortunately, graphql-dotnet doesn't seem to have that support. Having the schema, has some other advantages, in that you get VS-Code Apollo extension support etc. too, along with their GitHub bot to check for breaking changes. Also, it would be easier for people to learn because it aligns much more closely with other GraphQL implementations.

Could the learnings from this project, specifically the Signal-R bits and schema first approach be applied to graphql-dotnet?

It's certainly interesting and something I'll keep an eye on.

[RehanSaeed]

I forgot that existed! I suppose I forgot because it's not clear to me how to use the schema first approach using the ASP.NET Core server bits. If I get some time, I'll see if I can investigate.

[thangchung]

@joemcbride I have never known after read this issue. Thank you for your clarify 👍

[pekkah]

To see the differences in action go to https://github.com/pekkah/tanka-graphql-samples

• schema stitching/splitting /manipulation
• jwt based authentication
  Etc.

[pekkah]

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 specification.