Andy Knapp

:+1: Running into this on our project, too. Seems there's an existing issue as well, https://github.com/graphql-go/graphql/issues/629

Hey, I found that I could address this with my own helper like this: ```go func Nested(target interface{}, fieldRules ...*validation.FieldRules) *validation.FieldRules { return validation.Field(target, validation.By(func(value interface{}) error { valueV :=...

> @ki4jnq to access `FieldFive`, you may get nil pointer panic You mean when doing this: `&wrapper.FieldTwo.FieldFive`? True, your code would have to check that manually if it's a concern.

This was not obvious at all, and I too just spent several hours searching for a solution. Turns out, if you want to use your type with an Interface, you...