Open klefevre opened 8 years ago
Let's find an appropriate name together and change this indeed to avoid this compiler issue. Thanks for the hint.
PostalClient
seems the most legit.
Maybe a simple Client
would be ok because if a user has already a class named Client
he'd call Postal.Client
which is ok for me...
Any preference between both ?
hmmmmm PostalClient looks good to me. Let's do it
If a user want to create a class/struct/enum that as the same name as a public data type in Postal. The compiler will conflict with Postal class name and the Postal module.
e.g.
It is a known bug and I thought swift3 would fix this issue but it didn't and it becomes really annoying to whoever want to have a class named
Address
, orMessageHeader
(every public class in Postal) for a complete other purpose...To fix this I would propose to rename the
Postal
class forPostalClient
. @jeremiegirault WDYT ?