Dmitry VerkhoturovandUmputun
80c12a3f10
Bump Go dependencies in both backend/ and backend/_example/memory_store.
Notable updates:
- github.com/go-pkgz/lgr v0.12.1 -> v0.12.3
- github.com/klauspost/compress v1.18.2 -> v1.18.5
- github.com/PuerkitoBio/goquery v1.11.0 -> v1.12.0
- github.com/montanaflynn/stats v0.7.1 -> v0.9.0
- github.com/redis/go-redis/v9 v9.17.2 -> v9.18.0
- github.com/slack-go/slack v0.17.3 -> v0.21.1
- go.mongodb.org/mongo-driver v1.17.6 -> v1.17.9
- golang.org/x/crypto v0.48.0 -> v0.50.0
- golang.org/x/net v0.49.0 -> v0.53.0
- golang.org/x/image v0.36.0 -> v0.39.0
- golang.org/x/sys v0.41.0 -> v0.43.0
- golang.org/x/{oauth2,sync,text} minor bumps
Key markdown/sanitisation libs (bluemonday v1.0.27,
alecthomas/chroma/v2 v2.23.1, russross/blackfriday/v2 v2.1.0,
Depado/bfchroma/v2 v2.0.0) are already at the latest available
versions and were not bumped.
Verified the Chroma span-class allowlist regex in
backend/app/store/comment.go:128-131 is still fully in sync with
chroma/v2 types.go StandardTypes map (86 classes, byte-equal after
sorting). The inline comment references commit c263f6f which is
stale (Chroma is at v2 now), but the class list content is current.
Ran `go mod tidy` + `go mod vendor` + full race test suite on both
modules. All green. Added a reminder in CLAUDE.md that updating
backend/ Go modules also requires `go mod tidy` in
backend/_example/memory_store since the example module uses a
local replace directive and inherits indirect deps from the main
module.
1.1 KiB
1.1 KiB
Go-PKGZ/LGR Development Guidelines
Build & Test Commands
- Build:
go build -race - Test all:
go test -timeout=60s -race -covermode=atomic -coverprofile=profile.cov - Test single file:
go test -run TestName - Benchmark:
go test -bench=. -run=Bench - Lint:
golangci-lint run
Code Style Guidelines
- Go 1.21 compatibility required
- Maximum line length: 140 characters
- No package names with underscores
- Use early returns (enforced by prealloc linter)
- Test files use testify for assertions:
requirefor fatal assertions,assertfor non-fatal ones - Indent with tabs, not spaces
Error Handling
- FATAL logs to stderr and calls os.Exit(1)
- ERROR logs to both stdout and stderr
- PANIC logs stack trace and runtime info to stderr
- Stack traces for ERROR level can be enabled with StackTraceOnError option
Project Conventions
- Public API follows interface-based design (
lgr.Linterface) - Avoid global loggers, prefer dependency injection
- Functional options pattern for logger configuration
- Secret logging sanitization with
lgr.Secretoption