Unable to unit test package usage about mailerlite-go HOT 3 OPEN

@ajpetersons open to PR's to fix this 👍

Not sure how it could be done without a breaking change without looking into it in more detail

from mailerlite-go.

Would exporting the rootSubscriber and similar types that are returned by operations actually be breaking change for package users? Access to fields would remain the same, access to methods would be possible only if the method is exported. In my code I am unable to declare variable of type *rootSubscriber right now because that's an internal type, so there shouldn't be any issues with that. Maybe I'm missing something, please correct me if so.

The main benefit with this change would be that then I can write my own interface that SubscriberService implements. In main code I would supply struct from this package, but in unit tests I can use any struct I like as long as it satisfies the interface.

from mailerlite-go.

i suppose it would not be a breaking change thinking about this, could you maybe create a PR with what you are suggesting I will be happy to accept this if there are no breaking changes for users.

from mailerlite-go.