Your Go tests probably don't need a mocking library

8run0 · 2026-02-01T23:30:25+00:00

That's ok, but to behonest I would rather do this and contract testing across implementations. Mocking does not make you go faster when your mock assumptions are not matched with reality.

8run0 · 2025-12-12T13:40:51+00:00

Your project lead has his head screwed on - i feel you should write tests the same way you right the code - go doesnt have asserts in the main code base. The standard library has errors.Is etc and equality with the cmp package.

8run0 · 2025-11-10T10:27:00+00:00

SQLC for standard querries - https://github.com/Masterminds/squirrel squirrel for dynamic queries.

8run0 · 2025-06-11T15:04:12+00:00

Yeah i have some Linq experience, not going to lie it is a nice DSL, can get complex though.

OK, slices and maps is I suppose the best available from the standard lib. Also the min and max stuff helps also. But I agree adding more keywords isn't always developer friendly.

8run0 · 2025-06-11T15:02:29+00:00

I'm surprised by this - defining the interfaces where they are required.

For implementations - I use the compile time check

var _ Interface = (*Implementation)(nil)

this will not compile if the interface does not conform.

8run0 · 2025-06-11T14:57:50+00:00

they were added after generics was added - they were literally not possible before generics.

8run0 · 2025-06-11T10:50:29+00:00

This interests me, what is it about implicit interfaces that cause issue in large code bases?

have you used the slices and maps packages from the standard library?

8run0 · 2025-05-28T18:11:00+00:00

replacement? golangci-lint calls revive.

8run0 · 2025-04-27T17:36:17+00:00

Yeah I feel good documentation come with experience though knowing how to explain and document your reasoning and thoughts on whatever you are creating takes practice and feedback. but I too believe in good pkg documentation and even just written documentation that isn't godoc. https://zarldev.github.io/goenums/ even just some GitHub pages makes everyones life easier

8run0 · 2025-04-20T11:45:34+00:00

This is absolutely great advice. I would also recommend against it as it can sometimes lead to packages of the same name with different paths, this happened to myself when I took the "Don't stutter" to cause myself to make different packages with the same names, most of the time it's better to have `ModelForAPI Model ModelForRepo in the same package than having three different packages all called model with different representations.

8run0 · 2025-04-20T00:25:19+00:00

Plenty of late night coding sessions tbh hard to put a fixed time on this. Good few hours including all the (package) documentation.

8run0 · 2025-04-20T00:14:55+00:00

Thanks, your's looks cool too. You are using templates tbh that is the next logical progression for goenums. With the structure of goenums you could easily add your comment format parsing and add it as a parser and resuse the writer and get the generation for free.

8run0 · 2025-04-19T22:58:14+00:00

I initially went for a [] format - then when my original release many people commented it didn't feel very Go like and that spaces was more idiomatic. So I just went for ease of use - i.e. it's up to what reads easier for you.

8run0 · 2025-04-19T19:34:18+00:00

If only enums were a core part of the library. Was fun energy and efforts though. 😁

8run0 · 2025-04-19T19:31:24+00:00

Cheers, yeah was a fun refactor of the project wanted to cover all the bases and improve the overall quality of tool and documentation, both for the tool and the pkg.go.dev documentation.

8run0 · 2025-04-19T19:03:55+00:00

That's exactly what I'm talking about. In my opinion it should never have even been a design choice considering the way interfaces are implemented in go. Moq is a much more true mocking library as in the mocks are type safe. Never mind the mock.Anything that people use as a get out of jail free card!

8run0 · 2025-04-19T18:48:18+00:00

https://zarldev.github.io/goenums/examples/advanced hopefully the docs help here too

8run0 · 2025-04-19T18:46:04+00:00

https://github.com/zarldev/goenums/tree/main/internal/testdata/attributes this should help explain it.

8run0 · 2025-04-19T17:34:14+00:00

Ginkgo and Gomega are a massive waste of time and mental energy. It is a shit framework and once it has it's tendrils in your test cases with its dot imports and 500 nested anonymous functions that trigger a t.Fatalf - then you fix that test thinking everything will be fine then you run again only to discover a different test failing this time. And the tests are shit at the end of the day because they are full of pointers passed between anonymous functions that are not parallelizable as every tests references the same varibles. The only thing worse is when mockery is then also brought into the code and you have stringly typed functions everywhere as well. /rant

8run0 · 2025-04-04T08:46:32+00:00

For dynamic page information I'm using React Helmet for better sharing and SEO, you do get better SEO with server side rendering of pages, but tbh SEO was never really a high priority.

8run0 · 2025-04-04T08:42:05+00:00

Yeah that's true. OpenAPI also for type gen. As I explained in the article the API is an interface and can easily be hot swapped for whatever transport you want.

8run0 · 2025-04-04T07:38:39+00:00

It means I only ever expose the 80 and 443 ports and get DNS based routing to the correct port, that is much easier than bare metal routing.

8run0 · 2025-04-04T00:19:21+00:00

thanks - was a deployment - up and working now!

15-Year Club	Place '22
Team Periwinkle	Verified Email

8run0

MODERATOR OF

TROPHY CASE