Just conform to the spec :
7.1.2 If an error can be associated to a particular point in the
requested GraphQL document, it should contain an entry with the key
locations....
Coverage remained the same at 92.376% when pulling 3adb2f5581b54fbf4fc75e4545cf3b82b6cb8a6f on lvjp:master into 9441c498a148d34c007886e14295e13eb3efc340 on graphql-go:master.
Do not emit JSON when there is no error locations
Just conform to the spec : 7.1.2 If an error can be associated to a particular point in the requested GraphQL document, it should contain an entry with the key locations....