GraphQL on Azure: Part 5 – Can We Make GraphQL Type Safe in Code

This content originally appeared on Posts on LINQ to Fail and was authored by Posts on LINQ to Fail

I’ve been doing a lot of work recently with GraphQL on Azure Functions and something that I find works nicely is the schema-first approach to designing the GraphQL endpoint. The major drawback I’ve found though is that you start with a strongly typed schema but lose that type information when implementing the resolvers and working with your data model. So let’s have a look at how we can tackle that by building an application with GraphQL on Azure Functions and backing it with a data model in CosmosDB, all written in TypeScript.

This content originally appeared on Posts on LINQ to Fail and was authored by Posts on LINQ to Fail