Last week I had the incredible opportunity to speak at .NET Conf on An Introduction to GraphQL in .NET Core. It was certainly an novel experience to giving a talk from an empty Pushpay meeting room to an unknown amount of people.
I’m pleased to announce that I’ll be speaking in a few weeks at the Microsoft virtual conference .NET Conf! This looks like it’ll be a great conference that covers a wide range of subjects and also includes the launch of .NET Core 3.0.
Approval Tests or Snapshot Tests are in my opinion a vital part of the testing ecosystem that can service a number of uses cases. In this post I’ll introduce the concepts and discuss some of the scenarios we may want to employ them to best effect.
In my last post on Exposing Validation Metadata in GraphQL I showed how we can expose validation metadata from the server to the client in order to have to only define our validation rules once. In this post I’ll show how to autoamically enforce those validation rules on the server.
When we do input validation in our applications we want them on both the client and server for a couple of key reasons: