FactbirdHQ/atat

Consider dropping AtatClient trait

Closed this issue · 1 comments

I am not convinced the AtatClient trait brings anything to the table, that couldn't be solved using the concrete type?

Consider removing the trait entirely, in order to just make users use the concrete atat::Client type instead.

Closing this, as the concrete atat::Client type would involve lots of generics