010: internal package gotchas

I talk about how the internal package can be used wrongly. I recently had to expose a Go package that I never thought would be expose, hence I've heavily used the internal package, a bad decision.

Show Notes

I recently created an exportable Go package from StaticBackend, an open source backend API which was self-hosted.

I ended up using the internal package way to heavily and this design decision bite me when I decided to create an exportable package. Now all things that needed to be expose that was in the internal package had to be refactored into their own packages.

Links:

• StaticBackend repo
• Go package

Creators & Guests

Host

Dominic St-Pierre

Go system builder - entrepreneur. I've been writing software systems since 2001. I love SaaS, building since 2008.

What is go podcast()?

15 minutes news, tips, and tricks on the Go programming language.