jterry75
commented
3 years ago As a second comment prefer the use of the /internal/pkg-name to create componentization of the unsafe/com/etc code to make units more testable and maintainable without exposing a public surface area API
In my non-professional experience with golang the packages grow over time in a single repo which makes it hard starting off with root packages. For location especially for this as an sdk package I would recommend we start off with a /pkg/fabricclient or something location to avoid a root package. Makes it easier to add /tools, /cmd etc later