No support for vendoring (i.e., /vendor/ directory, previously called GO15VENDOREXPERIMENT).

The documentation for https://godoc.org/github.com/kubernetes/kubernetes/pkg/api/resource#NewQuantityFlagValue links to https://godoc.org/github.com/spf13/pflag#Value. I expect the documentation to link to https://godoc.org/github.com/kubernetes/kubernetes/vendor/github.com/spf13/pflag. The latter is what the go tool will use when building the api/resource package.

[josephspurrier]

Yeah, I think it would make sense if dependencies were vendored, the documentation would be built from them. For instance, I have vendored dependencies and since they are my own local packages, no documentation shows at all because it's looking online for them: https://godoc.org/github.com/josephspurrier/gowebapp

This is not a feature of godoc by default, but I feel like it would be a good addition.

[dmitshur]

@josephspurrier Agreed, that should work.

This issue can be summarized as /vendor/ directory is not supported.

That feature didn't exist in Go when gddo was created, and no one has added support for it to gddo yet.

[dmitshur]

There is some minimal support for /vendor/ directory in determining the score of a package for ranking/display purposes.

gddo/database/index.go

Line 169 in aa8084e

vendorPat.MatchString(pdoc.ImportPath) {

gddo/database/index.go

Lines 215 to 216 in aa8084e

	if vendorPat.MatchString(p) {
	// Penalize packages that import vendored packages.

But that's where support currently stops.