Armin RonacherFor converting my internal errors to something for the API, which of those options is what I should be using in Go? (Or am I doing this completely incorrectly and there is a better option)
Henrik Binggl 💻 🐈@mitsuhiko Option 2 (idiomatic error check); the std/low-level way is to use https://pkg.go.dev/net/http#Error, don’t know about the router/framework used where web.ExposeError is available.
@henrikb web.ExposeError is just my function that converts my internal errors on the db layer to http.Error
@mitsuhiko the idiomatic error check is awkward first and so verbose, but I prefer it now over exceptions in other languages.
Chris L. Barnes@henrikb @mitsuhiko Ever tried discriminated unions, like in Rust?
Glenjamin@mitsuhiko personally I prefer 1, but Go people will probably say 2 for hand wavy “idiomatic” reasons
Timo Zimmermann@mitsuhiko Option 2 is what I would expect reading Go code. Option 1 would (no matter how often I’ve seen this pattern in other languages) take some mental capacity to parse.
dan@mitsuhiko option 2 is more immediately clear to me. I don’t know under what conditions `web.ExposeError` returns true without further investigation.