What version of Go are you using (go version)?

go version go1.11 linux/amd64

Does this issue reproduce with the latest release?

yes

What did you do?

package foo

type t struct {
	X int
}

type Config struct {
	t
	Y int
}

$ go doc foo.Config

What did you expect to see?

The current output is not bad, but not perfect.
The reason is the field Config.X is also exported, but it is not mentioned in the printed doc.
Users of the foo package must read code to know that the field Config.X is usable.

What did you see instead?

package foo // import "foo"

type Config struct {
	Y int
	// Has unexported fields.
}