When designing a schema using interfaces, it's possible to find that documenting across the implementing types is a lot of work. Here's an example:

interface Animal {
   "The scientific classification for this Animal"
   breed: String
}

type Dog implements Animal {
   breed: String
   knownTricks: [Trick]
}

type Cat implements Animal {
   breed: String
   zoomieSchedule: [DateTimeRange]
}

type Bird implements Animal {
   breed: String
   sightings: [String]
}

In the example above, breed: String is defined on the interface Animal which is implemented by three types. When inspecting breed on Dog in GraphiQL, there is no documentation because the developer has only documented the Animal. To see the comment, the end user must know that the Animal interface is documented, and navigate to the type to see the comment. We could save the developer and end-user some time by offering the ability to inherit the documentation comments, when there are no explicit comments on an implementing type.

What do folks think? Does it make sense that when Cat.breed is not documented, to inherit the comments from Animal.breed? Is this functionality desired in graphql-java? In this case, since Cat.breed has no comments, we could inherit the comment from Animal.breed.