We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Following the addition of OSX (now macOS) and tvOS compatibility, it seems to appropriate to rename the targets and schemes as follows:
SwiftyStoreKit
SwiftyStoreKitIOS
SwiftyStoreKitOSX
SwiftyStoreKitMacOS
SwiftyStoreKitTV
SwiftyStoreKitTvOS
This should not be a code breaking change for clients as the module would be imported as import SwiftyStoreKit as before.
import SwiftyStoreKit
The folder structure could also be updated:
SwiftyStoreKitIOS.h
Info.plist
SwiftyStoreDemo
SwiftyStoreKitDemoIOS
SwiftyStoreOSXDemo
SwiftyStoreKitDemoMacOS
The above should bring more consistency to the naming conventions in SwiftyStoreKit. Feedback is appreciated about this proposal.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Following the addition of OSX (now macOS) and tvOS compatibility, it seems to appropriate to rename the targets and schemes as follows:
SwiftyStoreKit
->SwiftyStoreKitIOS
SwiftyStoreKitOSX
->SwiftyStoreKitMacOS
SwiftyStoreKitTV
->SwiftyStoreKitTvOS
This should not be a code breaking change for clients as the module would be imported as
import SwiftyStoreKit
as before.The folder structure could also be updated:
SwiftyStoreKitIOS
folder to includeSwiftyStoreKitIOS.h
andInfo.plist
files.SwiftyStoreKitOSX
folder toSwiftyStoreKitMacOS
SwiftyStoreKitTV
folder toSwiftyStoreKitTvOS
SwiftyStoreDemo
folder toSwiftyStoreKitDemoIOS
SwiftyStoreOSXDemo
folder toSwiftyStoreKitDemoMacOS
The above should bring more consistency to the naming conventions in SwiftyStoreKit. Feedback is appreciated about this proposal.
The text was updated successfully, but these errors were encountered: