That’s a bingo! Yeah I decided to dip my toes into Go by writing a simple library on a topic I was learning about

I don’t think libraries should log by default

That’s a fair point, interfaces are still a concept that boggle my mind a bit, but maybe this is the problem that will help me actually grasp them. Thanks!

there’s no explanation of what this is supposed to do.

Totally right, sorry about that, I’ll update the Github, but it brief this is a library that’s supposed to help a developer set up a Role Based Access Control system for an API for web service. Role Based Access Control is a method of access control whereby (And this is my very beginner’s understanding of it) users are assigned roles, and these roles are in turn issued different permissions based off what that role is supposed to have access to. When checking if a user is authorized access to a certain resource, the roles assigned to them are checked for the permissions needed for the resource. If they have permission then they are granted access to the resource, otherwise they are denied access.

This library manages roles, permissions assigned to roles, and checking of permissions against roles via an http middleware.

Then, there’s no main function. Where’s the entry point? This is a bit where I’m doubting myself now. Maybe go has changed, but when I was writing it, it requires a main function to even run.

Well, this is supposed to be a library that’s used by other people, so it has no main function itself, rather it’s called by other people

The tutorial series by DivRhino was really helpful for me – https://divrhino.com/articles/rest-api-docker-go-fiber-from-scratch – she has several tutorials that build on each other.