internal/pkgdoc: handle IndexListExpr
This fixes the panic occuring when the documentation generator
(pkgdoc) processes methods defined on generic types with multiple
type parameters (e.g., func (T[A, B]) M() {}).
The pkg.go.dev (pkgsite) is the default documentation serer and
go.dev/pkg/... are redirected to pkg.go.dev/....
However, the pkgdoc package is still used in certain cases:
- golang.google.cn serves package documentation directly using pkgdoc.
- when explicitly requested via `?m=old` (https://go.dev/pkg/fmt/?m=old)
- local development
Fixes golang/go#80430
Change-Id: I4d12c7d20ca74da4f95eb40dbb4f5e964373eeef
Reviewed-on: https://go-review.googlesource.com/c/website/+/801540
Reviewed-by: David Chase <drchase@google.com>
LUCI-TryBot-Result: golang-scoped@luci-project-accounts.iam.gserviceaccount.com <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
This repo holds content and serving programs for the go.dev and golang.org web sites.
Content is in _content/ (go.dev) and tour/ (go.dev/tour). Server code is in cmd/ and internal/.
To run the combined go.dev+golang.org server to preview local content changes, use:
go run ./cmd/golangorg
The supporting programs cmd/admingolangorg and cmd/googlegolangorg are the servers for admin.golang.org and google.golang.org. (They do not use the _content/ directories.)
Each command directory has its own README.md explaining deployment.
This repository uses eslint to format JS and TS files, and stylelint to format CSS files.
See also:
It is encouraged that all JS, TS, and CSS code be run through formatters before submitting a change. However, it is not a strict requirement enforced by CI.
./npm install./npx eslint [options] [file] [dir]
./npx stylelint [input] [options]
TypeScript files served from _content are transformed into JavaScript. Reference .ts files in html templates as module code.
<script type="module" src="/ts/filename.ts">
Write unit tests for TypeScript code using the jest testing framework.
./npx jest [TestPathPattern]
Each time a CL is reviewed and submitted, the code is deployed to App Engine. See cmd/golangorg/README.md for details.
This repository uses Gerrit for code changes. To learn how to submit changes to this repository, see https://go.dev/doc/contribute.
The git repository is https://go.googlesource.com/website.
The main issue tracker for the website repository is located at https://go.dev/issues. Prefix your issue with “x/website:” in the subject line, so it is easy to find.