Closed johnpeeke closed 44 minutes ago
Related Issues and Documentation
(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)
If you have a go.mod file, and it does not specify a go version, the default is to assume that you are using an old version of Go, specifically 1.16. For cases like enhanced routing patterns, you will therefore get the behavior of the Go 1.16 standard library. This is working as intended.
Go version
go version 1.23
Output of
go env
in your module/workspace:What did you do?
`func main() { apiCfg := &apiConfig{} apiCfg.fileserverHits = atomic.Int32{}
}`
Navigate to any endpoint using the new enhanced routing pattern introduced in go version 1.22 (i.e. Get /healthz)
go.dev/play
What did you see happen?
I receive a 404 error
What did you expect to see?
I expected an OK response. I receive the correct response only if go version 1.22 or 1.23 is explicitly set in go.mod. I did not expect to have to explicitly set this as only go version 1.23 is installed on my system.