package structure

[dividinglimits]

Separate your project into behaviors. Currently I perceive this as a single monolithic package that could have been made into multiple ones.

https://medium.com/@benbjohnson/standard-package-layout-7cdbc8391fc1
https://dave.cheney.net/2014/12/01/five-suggestions-for-setting-up-a-go-project

[genesor]

Thanks for pointing this out.

I was thinking of adding a mock package to allow easy implementation and testing when integrating the package but I was wondering if people won't prefer making their own mocks.

For the split of the package itself, I'm thinking of a split by service, one sub-package by Twilio entity. eg: one for phonenumbers one for sms one for voice etc...

WDYT ?