Swiftpack.co - Swift Packages by rockbruno

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. - Improved how the SWIFTSHIELDED property is added - @strfn - Fixed SwiftShield not handling files with escaped spaces correctly - @ptwoms - Added `ignoreNames`, a field of names that should *not* be obfuscated. @andreiChis70 Fixed Xcode 12 builds failing by @ekam123 Instance, class and global properties will now be obfuscated, with the exception of properties under types that inherit from `Codable` and classes exposed to Objective-C. For more information, check the limitations document. Although we have lots of tests checking if property obfuscation is working correctly, we're still not certain that we covered all edge cases. If you don't feel like gambling on this, it might be better to use version `4.0.3`. Fixed an issue where `--ignore-public` failed on references that contained multiple attributes (like `public static`) - `--ignore-public` will now correctly avoid enums Files containing emojis will now be correctly obfuscated. This includes types that have emojis in their names and everything else. With this release, the relevant limitation was removed from SOURCEKITISSUES.md. SwiftShield has been completely remade. The first version was highly untested, and new features were very hard to develop and maintain. The code is now highly tested, including tests that run `xcodebuild` and SourceKit themselves. Now, we're able to know if SwiftShield works correctly with newer versions of Xcode, and new features are easy to test. Functionality is mostly the same, but the usage details changed. Check the README for the newest set of instructions. - `-sdk` renamed to `--ignore-public` - Removed manual mode. Manual mode was created because the automatic mode was extremely unstable. Now that SourceKit works (mostly) correctly, the manual mode lost its purpose. If you were relying on it, let me know. - Removed Storyboard Obfuscation. This feature was untested, extremely hard to maintain and had tons of untreated edge cases. Since the usage of Storyboards is almost nonexistent in large projects (the target of SwiftShield), the feature was removed. SwiftShield will now only support view code obfuscation. - Revamped the example project. Fixed a problem with enum elements - Enums will be obfuscated, expect ones with the `CodingKeys` suffix - @hwdavr

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. This version (hopefully) works with future Xcode upgrades. Fixed older versions not working correctly with danger-SwiftInfo. You need to use danger-SwiftInfo 0.1.0 for it to work with this version. - Fixed issues with how arguments were parsed - You can now set custom Slack message prefixes - @yhkaplan - Fixed issues with asset catalog detections - @rogerluan Fix errors with resolving `Xcodeproj` in Xcode 11 projects which contain Swift packages. - @joeboyscout04

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. - Removed `AnyDependenciesInitializer` - Removed `AnyFeature` - Remove the `Dependency` protocol - Added the `@Dependency` property wrapper The ugly boilerplate of this framework like `AnyFeature` and `AnyDependenciesInitializer` are a result of the Swift compiler's limitation on generics. In this PR, I tested the creation of features using property wrappers instead of the usual dependencies struct. It worked, and by using Mirror to resolve the properties, I am able to drop the associated type from the `Feature` and all other ugly type-erasures alongside it :) Here's how features looked before this change: ```swift private enum ProfileFeature: Feature { struct Dependencies { let client: HTTPClientProtocol } static var dependenciesInitializer: AnyDependenciesInitializer { return AnyDependenciesInitializer(Dependencies.init) } static func build( dependencies: ProfileFeature.Dependencies, fromRoute route: Route? ) -> UIViewController { return ProfileViewController(dependencies: dependencies) } } ``` With property wrappers, I can remove all the boilerplate: ```swift private struct ProfileFeature: Feature { @Dependency var client: HTTPClientProtocol func build(fromRoute route: Route?) -> UIViewController { return ProfileViewController(client: client) } } ``` The `Feature` became a struct to make use of the compiler's synthesized initializers, and the properties are automatically resolved by RouterService. You don't need to create the annoying `dependenciesInitializer` type anymore and you don't need to worry about features that have zero or one dependency. This simplified structure makes it easier to develop and test new features. If you want to test `build()`, you can do either: ```swift let feature = ProfileFeature() feature.resolve(withStore: yourCustomStore) feature.build(...) ``` or the more useful injection through the init: ```swift let feature = ProfileFeature(client: .init(resolvedValue: myMockClient)) feature.build(...) ``` The original `Dependency` protocol was also removed because it was just an alias for `AnyObject`. - Dependencies are now registered with a closure instead of a plain instance. RouterService now retains dependencies weakly, meaning that your instances will correctly deallocate if no features are using them, and allocate again if a feature requests it again in the future. Before this change, any dependency would be alive 100% of the time. - Updates to the Example project. There is now a more complete example.