Returning nil as response body causes 500

[outofthisworld]

Some package level serialisation/reflection issue (I believe potentially to do with the SchemaLinkTransformer) is making a return of nil cause a 500 error as a response body.

Personally, I think this should be handled internally by the package to Serialise to null, to avoid redundant and unnecessary checking in every handler.