Release 1.4.5
Resolves an issue that may occur when more than one module defines the class Order
in an Objective-C interface. This can occur when importing Objective-C headers into your project either explicitly or via CocoaPods. The error looks like the following:
'Order' has different definitions in different modules; first difference in module 'OtherModule.swift'
With this patch:
- Swift generated Objective-C interfaces will no longer expose an
Order
class, insteadBTNOrder
- String lookups for the class
Order
in Objective-C will no longer find the ButtonMerchantOrder
class - If you are using the ButtonMerchant
Order
class in Objective-C, the module aliasesOrder
→BTNOrder
by default
Note: If you have an Order
class in Objective-C in the same file you're using the ButtonMerchant Order
class, you can #undef Order
in that file and replace instances of ButtonMerchant Order
with BTNOrder