Swiftpack.co - Swift Packages by freshOS

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. - Undeprecates the double dash "--" operator to address compile time issues as explained in https://github.com/freshOS/Stevia/pull/165 Thanks @cowgp for this release. -Adds `Int` and `CGFloat` variants for SteviaLayoutAnchor operators. (Fixes https://github.com/freshOS/Stevia/issues/153) Congrats @edulpn for this release 👏 Updates to swift-tools-version:5.3 Thanks @moliya for noticing `CGFloat` values were broken in `layout` blocks, this is now fixed 🎉 ⚠️ A serious bug has been found in this release, please use 5.0.1 instead ⚠️ Bug found that can break your layouts -> https://github.com/freshOS/Stevia/pull/141 - Adds support for `CGFloat` for all apis - `%` constraints can now be used in `layout` blocks for margins, height & spaces - `sv()` is renamed to `subviews()` for clarity - `subviews()` has now its function builder counterpart: `subviews{}` (no more commas!) - `layout()` has now its [function builder](https://github.com/apple/swift-evolution/blob/9992cf3c11c2d5e0ea20bee98657d93902d5b174/proposals/XXXX-function-builders.md) counterpart: `layout {}` - `fillVertically(m:)` is renamed to `fillVertically(padding:)` - `fillHorizontally(m:)` is renamed to `fillHorizontally(padding:)` - `fillContainer(x)` is renamed to `fillContainer(padding: x)` - `centerHorizontally(x)` is renamed to `centerHorizontally(offset: x)` - Double dash `--` operator is renamed in hyphen bullet for better compile times. (auto replace) - Adds UIStackView `arrangedSubviews {}` function builder Swift Package Manager is now the official way to install Stevia 🎉. In order to use other package managers, see previous versions. Onwards ! ✨ - Builds the pre-built framework with Xcode 11.2.1 & Swift 5.2.1 - Fixes the issue described in #123 where equation api had bugs when using `>=` & `<=` with single values. Props @jsonfellin for noticing, thanks @excursus for chiming in 🙏 Before ```swift view.Width >= 30 ≠ view.width(>=30) view.Width >= 30 was equivalent to view.Width >= Width + 30 (Wrong) view.Botton >= 100 was equivalent to view.Bottom >= Bottom + 100 (Wrong) view.Right >= 100 was equivalent to view.Right >= Right + 100 (Wrong) ``` Now ```swift view.Width >= 30 == view.width(>=30) view.Height <= 100 == view.height(<=100) view.Botton >= 100 == view.Bottom >= Bottom - 100 view.Right >= 100 == view.Right >= Right - 100 ``` - Big thanks @lukysnupy for his first contribution on improving our SPM integration 👏

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. -Fixes https://github.com/freshOS/KeyboardLayoutGuide/pull/39 thanks @stuartcamerondeakin 👏 Swift Package Manager is now the official way to integrate `KeyboardLayoutGuide` 🎉 Other package managers (Carthage and Cocoapods) are now deprecated in favour of the official way. - Improves the api for using both safeArea and no safeArea with `keyboardLayoutGuideNoSafeArea` #28 - Fixes an animation glitch happening with a secured Textfield #32 - Builds pre-built framework with Xcode 11.3 Big thanks to @EfraimB & @abekert for this release 👏 🎉 - Builds with Xcode 11 & Swift 5.1 - Adds SPM support (thanks to @dstranz) - Adds opting out from default safe Area (Thanks to @moyerr) Thanks @numen31337 & @xzeror for the release - Migrate to Swift 4.2 & Xcode 10 - Courtesy of @thomas-sivilay 🚀 Kudos to @ali312 for finding and fixing a nasty iPad slide over bug 👍 Fixes iOS 11 bug where `keyboardWillChangeFrame` is not called

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. - Bumps to Swift version to 5.6 - min supported versions: - iOS 14 - MacOS 11 - tvOS 14 - watchOS 7 Updated for iOS15 🎉 - Fixes #70 annoying Xcode warning `The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.2.99.` Thanks @simonbromberg - Fixes Xcode13/iOS15 build by renaming `await` by `awaitPromise` #72 Thanks @RocZhang9673 The project now follows the Swift package Manager conventions which simplifies package maintenance. Swift Package Manager is now the official way to integrate `Then` on all platforms. 🎉 Onwards ! ✨🥂 - Updates Package.swift - Build with Xcode 11.3 & Swift 5.1.3 - Adds watchOS support, Thanks to @jos76 👏✨ - Updates for Xcode 11 & Swift 5.1 - Renames framework from `then` to `Then` to comply to standards. thanks @MoveUpwardsDev 👍 Adds Swift 5 support courtesy of @bernardowilson 🎉

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. Replaces POST PUT PATCH `params` by `body` parameter with an enum (`.urlEncode` | `.json` | `.multipart`) Adds POST, PUT, PATCH `Encodable` body. Example: ```swift let data: Data = try await network.post("/users", body: Credentials(username: "john", password: "doe")) ``` where `Credentials` conforms to the `Encodable` protocol. - Fixes async await continuation error. Adds `jsonDecoderFactory` to provide your own `JSONDecoder`. ```swift network.jsonDecoderFactory = { let decoder = JSONDecoder() let df = DateFormatter() df.locale = Locale(identifier: "en_US_POSIX") df.dateFormat = "yyyy-MM-dd'T'HH:mm:ssZZZZZ" decoder.dateDecodingStrategy = .formatted(df) return decoder } ``` - Async-Await api is here 🎉 - async-await api is here ! - Fixes naming issues detailed here https://github.com/freshOS/Networking/issues/42 - Includes https://github.com/freshOS/Networking/pull/43 Thanks @elijah-rappaport - Bumps to 1.0.0, this has now been used in many production apps long enough 🚀 - Fixes "?" added at the end of GET requests without any params. Found by @adomingd and fixed by @workingDog - Solves #26 - Add the ability to retry a request with a middleWare via `requestRetrier` The typical example use case is reauthenticating before retrying a request: ```swift private var isRetrying = CurrentValueSubject<Bool, Error>(false) init() { restAPI.network.requestRetrier = { [unowned self] _, error in if self.isRetrying.value == true { return self.isRetrying.filter({ !$0 }).asVoid().eraseToAnyPublisher() } guard let error = error as? NetworkingError, error.status == .unauthorized else { return nil } return restAPI.authenticate().eraseToAnyPublisher() } } ``` Thanks @denis-obukhov for this improvement !

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. - Updates Support for Swift Package Manager - Builds with Xcode 11 & Swift 5.1 - Migrates to swift 4.2 & Xcode10 Supports Swift 4.1 and Xcode 9.3

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. Deprecating: - iOS < 12 - macOS < v10_13 - tvOS < 12 - watchOS < 4 as per Apple recommandations PrivacyInfo.xcprivacy Swift Package Manager is now the official way to install Arrow. 🎉 Legacy package managers Carthage & Cocoapods are now deprecated in favour of the official way. - Updates Package.swift - Builds with Xcode 5.3 & Swift 5.1.3 - Xcode11 & Swift 5.1 Updates the code to swift 5 🎉 - Migrates to Swift 4.2 & Xcode 10 🚀 - Updated for Swift 4.1 & Xcode 9.3

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. - Adds a way to add global parameters via `mandatoryQueryParams` Thanks to @Pafgz https://github.com/freshOS/ws/pull/68 - Allows configuration of a custom SessionManager Thanks to @brian-dlee https://github.com/freshOS/ws/pull/67 - Adds PATCH http verb support Kudos to @n13 https://github.com/freshOS/ws/pull/66 - Multipart put and post now accept an array of multipart data, with compatibility wrappers for the old single data API Kudos to @n13 https://github.com/freshOS/ws/pull/66 - Updates project for SPM support - Builds with Xcode 11.3 & Swift 5.1.3 - Builds with Xcode 11 & Swift 5.1 Adds Support for swift 5 🎉 - Migrates to Xcode 10 & Swift 4.2 🚀 Supports Swift 4.1 & Xcode 9.3 - Adds Support for Swift 4 & Xcode 9. Kudos to @LivioGama and @maxkonovalov for finding and fixing the issue 🎉 - Fixes retain cycle in `resolveOnMainThread` - Updates `then` version

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. # ⚠️ v 0.2 🏗 Please be aware that this is still very experimental 🔬. The actual api can and *will* change. This is not battle-tested and we advise you against using this in Appstore Apps (for now) ### Declarative Styling via Props 🎨 Applying styles directly on the UIKit elements was super handy in `v0.1` but came with major strings attached. Indeed, the styles blocks in the nodes **could only be called on the main thread**, because UIKit is meant to be accessed from the UI Thread (for the most part). Also, in order to compare styles, we needed to create a duplicate UIKit element (heavy) and look for differences on it. That's where `Props` come in! The idea is to have a Props layer, aka **a structure that defines an element's style**, that is `Equatable`. Being equatable, it becomes trivial to compare two buttons styles. For instance, you can just write : `let styleIsTheSame = (button.props == newButton.props)` Being Value-typed, it is also safe to process the diff in background ! Could we get all this goodness for free? Of course not, welcome to engineering. The major drawback is that we have to bridge every UIKit element property to its corresponding `Props` struct. However the properties supported can only get better with time classic escape hatch through refs will always be accessible to access UIkit elements if a property is not yet supported. This is worth it! ### A dead-simple declarative layout 📐 The coming version is switching from Autolayout (and Stevia) to a declarative layout. The new layout system is based on a super simple `Layout` struct, that, combined with classic `StackViews` enables 99.9% of layout cases. It is a value type, meaning it will be thread safe and thus enable comparison in a background thread :) ### Diffing on the virtual DOM. 🚀 With `elements`, `styling`, and `layout` purely **declarative**, **Value-Type** and **Equatable**, we can now safely put all the heavy duty stuff off to a background thread !!! In `v0.2`, the [diffing](https://facebook.github.io/react/docs/reconciliation.html) algorithm (also known as reconciliation) will run on the virtual DOM, on a background thread and only schedule UI changes on the UI thread. 🎉