You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think the interface should be part of the libary and can adhere to the principal. Checks should be made that the implemented struct methods satisfy the interface.
This would make mocking, for testing pruposes, easier, by having an "offical" and up to date interface to mock against.
Is your feature request related to a problem? Please describe.
The go doc reference for gocloak package describe the client like a GoCloak interface.
It seems to be a good approach to abstract the core Client.
The interface assume a succefull instantiate struct and a strong API Contract.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
I'm always frustrated when i manipulate the core struct instance with the tentation for changing the internal fields.
Whats is the motivation to expose the struct instead of Interface ?
Describe the solution you'd like
The change to an interface cause an error inside the options parameters for the NewClient method.
The solution should to have an internal type option.
I purpose you to make this rollback change.
i didn't find any resources about this topics ;)
The text was updated successfully, but these errors were encountered: