commit | d14b36d21f9c29e7fbc24ef0556d798b778fe725 | [log] [tgz] |
---|---|---|
author | Jamal Carvalho <jamal@golang.org> | Tue Dec 07 17:50:37 2021 +0000 |
committer | Jamal Carvalho <jamalcarvalho@google.com> | Wed Dec 08 18:01:05 2021 +0000 |
tree | 3a7f8fc269a9b44ca2aa851f240b3e99d1dcccb1 | |
parent | 0dd6a27c6afee039c4b4a23d2d27d09064062875 [diff] |
_content/js: fix playground request URL generation To verify that the backend param should not be set for a URL we must check for both null and undefined. Updating the if statements to check for falsey values instead of null. Change-Id: If58536e11e70e788976add41c60bb3688d50984e Reviewed-on: https://go-review.googlesource.com/c/website/+/370016 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Trust: Jamal Carvalho <jamalcarvalho@google.com> Run-TryBot: Jamal Carvalho <jamalcarvalho@google.com> TryBot-Result: Gopher Robot <gobot@golang.org>
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 prettier to format JS and CSS files.
See also:
The version of prettier
used is 1.18.2.
It is encouraged that all JS and CSS code be run through this before submitting a change. However, it is not a strict requirement enforced by CI.
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 main issue tracker for the website repository is located at https://github.com/golang/go/issues. Prefix your issue with “x/website:” in the subject line, so it is easy to find.