Swiftpack.co - Swift Packages by pointfreeco

Swiftpack.co is a collection of thousands of indexed Swift packages. Search packages.

Packages published by pointfreeco

pointfreeco/swift-composable-architecture 0.50.1
A library for building applications in a consistent and understandable way, with composition, testing, and ergonomics in mind.
⭐️ 8,066
πŸ•“ 1 week ago
πŸ”– Release Notes

Releases

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.
0.50.1
1 week ago
## What's Changed * Fixed: SwiftUI can write to bindings at inopportune times, like if a text field in a sheet is focussed, it will write to the binding _after_ the sheet has been dismissed. When using `IfLetStore`, this can lead to noisy runtime warnings emitted by TCA, where optional state driving the sheet is now `nil`, and thus the binding cannot write to state at this time. As a workaround, `IfLetStore` will now ignore actions sent through bindings when state is `nil` (https://github.com/pointfreeco/swift-composable-architecture/pull/1879). * Fixed: A bug in Swift 5.7 and earlier can cause the runtime metadata mechanism used by swift-case-paths to crash in release mode when an `Any` existential exists in the type data. Because `BindingAction` holds onto an `Any` under the hood, it could be responsible for the occasional crash in release mode when present in certain type layouts. We've worked around this bug to prevent crashes in release mode (https://github.com/pointfreeco/swift-composable-architecture/pull/1881). * Infrastructure: Fix docs link (thanks @Jager-yoo, https://github.com/pointfreeco/swift-composable-architecture/pull/1874); add note to reducer protocol dependency docs (https://github.com/pointfreeco/swift-composable-architecture/pull/1873); updated CoC to the latest Contributor Covenant. **Full Changelog**: https://github.com/pointfreeco/swift-composable-architecture/compare/0.50.0...0.50.1
0.50.0
2 weeks ago
## What's Changed * Added: `@BindingState` (renamed from `@BindableState` in this release) now conditionally conforms to `Sendable` (thanks @jshier, https://github.com/pointfreeco/swift-composable-architecture/pull/1834). * Added: SwiftUI Transaction helper APIs, including `Effect.transaction`, `ViewStore.send(_:transaction:)`, and `Effect.run { send in send(_:transaction:) }` (thanks @drucelweisse, https://github.com/pointfreeco/swift-composable-architecture/pull/1824). * Added: `Store.init` now takes a `prepareDependencies` block, for preparing the initial dependencies of a store (`TestStore` introduced a similar API earlier) (https://github.com/pointfreeco/swift-composable-architecture/pull/1844). * Added: `Effect.send` has been introduced as a new version of `Effect.init(value:)` (https://github.com/pointfreeco/swift-composable-architecture/pull/1859). `Effect.init(value:)` has been soft-deprecated and will be hard-deprecated soon, so prefer using `Effect.send` to synchronously feed actions back into the system. * Changed: The `@BindableState` property wrapper has been renamed to `@BindingState` (https://github.com/pointfreeco/swift-composable-architecture/pull/1855). * Changed: `TestStore` ergonomics have been improved to better surface when APIs are unavailable due to lack of an `Equatable` conformance (https://github.com/pointfreeco/swift-composable-architecture/pull/1857). * Changed: Alert modifiers now use `@StateObject` instead of `@ObservedObject` in iOS 15 and higher (https://github.com/pointfreeco/swift-composable-architecture/pull/1860). * Changed: Reducer builders have been rewritten to be more performant and to prepare for forthcoming Swift 5.8 changes (https://github.com/pointfreeco/swift-composable-architecture/pull/1863). If you notice any regressions in your app's reducer builders, please [let us know](https://github.com/pointfreeco/swift-composable-architecture/issues/new?assignees=&labels=bug&template=bug_report.yml). * Changed: The Composable Architecture has been updated to depend on [SwiftUI Navigation 0.6.0](https://github.com/pointfreeco/swiftui-navigation/releases/0.6.0) (https://github.com/pointfreeco/swift-composable-architecture/pull/1865). > **Warning**: This upgrade contains breaking changes that mostly do not affect the Composable Architecture, which the exception of its UIKit alert helper tools, which will now require you to handle a `nil` alert action for dismissal/cancel buttons with no action attached. * Fixed: #1802 introduced a slight regression in view store binding animation behavior, so it was reverted back to the original behavior (https://github.com/pointfreeco/swift-composable-architecture/pull/1845). * Fixed: `Effect` is now hard deprecation as planned (thanks @kalupas226, https://github.com/pointfreeco/swift-composable-architecture/pull/1822). * Fixed: The Composable Architecture now explicitly depends on Ordered Collections, rather than implicitly via its transitive dependency on Identified Collections (thanks @kalupas226, https://github.com/pointfreeco/swift-composable-architecture/pull/1828). * Fixed: `TestStore.receive` methods that take predicates and case paths no longer require `Action` equitability (https://github.com/pointfreeco/swift-composable-architecture/pull/1856). * Infrastructure: Removed and updated a few deprecated, flakey tests (https://github.com/pointfreeco/swift-composable-architecture/pull/1816). * Infrastructure: Added UI test to catch SwiftUI regressions (https://github.com/pointfreeco/swift-composable-architecture/pull/1815; thanks @tgrapperon in https://github.com/pointfreeco/swift-composable-architecture/pull/1819). * Infrastructure: Doc fixes (thanks @brennobemoura, https://github.com/pointfreeco/swift-composable-architecture/pull/1843). * Infrastructure: Document testing gotchas (https://github.com/pointfreeco/swift-composable-architecture/pull/1854). ## New Contributors * @jshier made their first contribution in https://github.com/pointfreeco/swift-composable-architecture/pull/1834 * @brennobemoura made their first contribution in https://github.com/pointfreeco/swift-composable-architecture/pull/1843 * @drucelweisse made their first contribution in https://github.com/pointfreeco/swift-composable-architecture/pull/1824 **Full Changelog**: https://github.com/pointfreeco/swift-composable-architecture/compare/0.49.2...0.50.0
0.49.2
4 weeks ago
## What's Changed * Fixed: A longstanding bug in SwiftUI can cause bindings to be evaluated in views that are no longer rendered. In apps built in the Composable Architecture, which provides flexible tools for deriving custom bindings, this could lead to accessing state that no longer exists, which at worst could try to evaluate an element of an array at an invalidated index, crashing the application. While this bug was fixed in 0.48.0, it introduced another regression and was reverted in 0.48.1. We have a new workaround (thanks @iampatbrown, https://github.com/pointfreeco/swift-composable-architecture/pull/1802), that appears to be more reliable and work in both cases. If you encounter any regressions in `ViewStore.binding` behavior in your applications, [let us know](https://github.com/pointfreeco/swift-composable-architecture/issues/new?assignees=&labels=bug&template=bug_report.yml)! * Fixed: `Dependencies` has been force-bumped to 0.1.2 to work around a regression in how effects inherit dependencies (thanks @tgrapperon, https://github.com/pointfreeco/swift-composable-architecture/pull/1813). **Full Changelog**: https://github.com/pointfreeco/swift-composable-architecture/compare/0.49.1...0.49.2
0.49.1
4 weeks ago
## What's Changed * Fixed: An internal test helper added in 0.49.0 could prevent builds from working. This has been fixed (https://github.com/pointfreeco/swift-composable-architecture/pull/1809). * Infrastructure: Fixed UIKit's "Navigate and Load" study (thanks @tgrapperon, https://github.com/pointfreeco/swift-composable-architecture/pull/1807). **Full Changelog**: https://github.com/pointfreeco/swift-composable-architecture/compare/0.49.0...0.49.1
0.49.0
4 weeks ago
## What's Changed * Changed: Depend on [swift-dependencies](https://github.com/pointfreeco/swift-dependencies). The `Dependencies` module has been extracted to its own library so that it can be used in non-TCA apps. **Full Changelog**: https://github.com/pointfreeco/swift-composable-architecture/compare/0.48.1...0.49.0
0.48.1
4 weeks ago
## What's Changed * Fixed: Reverted #1784, which introduced a regression in SwiftUI binding behavior (https://github.com/pointfreeco/swift-composable-architecture/pull/1799). **Full Changelog**: https://github.com/pointfreeco/swift-composable-architecture/compare/0.48.0...0.48.1
0.48.0
4 weeks ago
## What's Changed * Changed: `withTaskCancellation(id:)` now executes on the current executor without suspension (https://github.com/pointfreeco/swift-composable-architecture/pull/1779). * Deprecated: `Effect` has been temporarily deprecated for `EffectTask` to prepare for renames [coming in 1.0](https://github.com/pointfreeco/swift-composable-architecture/discussions/1477) (https://github.com/pointfreeco/swift-composable-architecture/pull/1788). * Deprecated: `EffectPublisher` is now soft-deprecated (https://github.com/pointfreeco/swift-composable-architecture/pull/1791). * Deprecated: The `async` version of `ActorIsolated.withValue` has been deprecated. It can introduce re-entrancy bugs. Instead, we have introduced a synchronous version (https://github.com/pointfreeco/swift-composable-architecture/pull/1792). * Fixed: `@Dependency(\.openURL)` is now supported in App extensions (thanks @tgrapperon, https://github.com/pointfreeco/swift-composable-architecture/pull/1714). * Fixed: `ButtonRole` and `Button` deprecation warnings have been silenced (thanks @kgrigsby59, https://github.com/pointfreeco/swift-composable-architecture/pull/1715). * Fixed: A longstanding bug in SwiftUI can cause bindings to be evaluated in views that are no longer rendered. In apps built in the Composable Architecture, which provides flexible tools for deriving custom bindings, this could lead to accessing state that no longer exists, which at worst could try to evaluate an element of an array at an invalidated index, crashing the application. This bug has now been worked around to avoid such crashes. (Thanks @barabashd, https://github.com/pointfreeco/swift-composable-architecture/pull/1784; https://github.com/pointfreeco/swift-composable-architecture/pull/1785). * Fixed: The predicated-based version of `TestStore.receive` now properly evaluates the given predicate (thanks @pyrtsa, https://github.com/pointfreeco/swift-composable-architecture/pull/1780). * Infrastructure: Fix typos, etc., in documentation, README, and tests (thanks @ZevEisenberg, https://github.com/pointfreeco/swift-composable-architecture/pull/1701; @tgrapperon, https://github.com/pointfreeco/swift-composable-architecture/pull/1702; @yimajo, https://github.com/pointfreeco/swift-composable-architecture/pull/1725; @yuanhang, https://github.com/pointfreeco/swift-composable-architecture/pull/1762; @kalupas226, https://github.com/pointfreeco/swift-composable-architecture/pull/1764; @dy-kim, https://github.com/pointfreeco/swift-composable-architecture/pull/1773; @Iikeli, https://github.com/pointfreeco/swift-composable-architecture/pull/1776; https://github.com/pointfreeco/swift-composable-architecture/pull/1787; @jeffersonsetiawan, https://github.com/pointfreeco/swift-composable-architecture/pull/1793). * Infrastructure: Fix todo deletion in Todos sample app when the list is filtered (https://github.com/pointfreeco/swift-composable-architecture/pull/1696). * Infrastructure: Bump SwiftUINavigation and update examples (thanks @iampatbrown, https://github.com/pointfreeco/swift-composable-architecture/pull/1760). ## New Contributors * @ZevEisenberg made their first contribution in https://github.com/pointfreeco/swift-composable-architecture/pull/1701 * @yuanhang made their first contribution in https://github.com/pointfreeco/swift-composable-architecture/pull/1762 * @dy-kim made their first contribution in https://github.com/pointfreeco/swift-composable-architecture/pull/1773 * @Iikeli made their first contribution in https://github.com/pointfreeco/swift-composable-architecture/pull/1776 * @barabashd made their first contribution in https://github.com/pointfreeco/swift-composable-architecture/pull/1784 * @pyrtsa made their first contribution in https://github.com/pointfreeco/swift-composable-architecture/pull/1780 **Full Changelog**: https://github.com/pointfreeco/swift-composable-architecture/compare/0.47.2...0.48.0
0.47.2
10 weeks ago
## What's Changed * Fixed: Dependency values test context is no longer implicitly inferred, which could cause unexpected behavior for host applications that run during tests (https://github.com/pointfreeco/swift-composable-architecture/pull/1686). **Full Changelog**: https://github.com/pointfreeco/swift-composable-architecture/compare/0.47.1...0.47.2
0.47.1
11 weeks ago
Pinned SwiftUINavigation to its newest release, [0.4.2](https://github.com/pointfreeco/swiftui-navigation/releases/tag/0.4.2), to fix an issue with `ButtonState`'s equatable conformance. **Full Changelog**: https://github.com/pointfreeco/swift-composable-architecture/compare/0.47.0...0.47.1
0.47.0
11 weeks ago
## What's Changed * Depend on SwiftUINavigation for TextState, AlertState, etc... in https://github.com/pointfreeco/swift-composable-architecture/pull/1685 The `TextState`, `AlertState` and `ConfirmationDialogState` types have been moved out of the library and into [SwiftUINavigation](http://github.com/pointfreeco/swiftui-navigation). It should be completely backwards compatible, and you should not have to change your code, but let us know if you encounter problems. **Full Changelog**: https://github.com/pointfreeco/swift-composable-architecture/compare/0.46.0...0.47.0
iOS macOS watchOS tvOS
pointfreeco/swift-snapshot-testing 1.11.0
πŸ“Έ Delightful Swift snapshot testing.
⭐️ 3,030
πŸ•“ 2 weeks ago
πŸ”– Release Notes

Releases

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.
1.11.0
2 weeks ago
## What's Changed * Added: Image paths in Xcode XCTest output are now clickable (thanks @RufusMall, https://github.com/pointfreeco/swift-snapshot-testing/pull/675). * Fixed: Silenced SPM warnings by excluding snapshots and fixtures in Package manifest (thanks @valeriyvan, https://github.com/pointfreeco/swift-snapshot-testing/pull/684). * Fixed: 1.10.0 erroneously bumped platform requirements. This release reverts compatibility to align with previous versions (https://github.com/pointfreeco/swift-snapshot-testing/pull/698). * Infrastructure: Fixed Ubuntu CI by locking version (https://github.com/pointfreeco/swift-snapshot-testing/pull/685). ## New Contributors * @RufusMall made their first contribution in https://github.com/pointfreeco/swift-snapshot-testing/pull/675 **Full Changelog**: https://github.com/pointfreeco/swift-snapshot-testing/compare/1.10.0...1.11.0
1.10.0
20 weeks ago
## Changes that may affect your build requirements - The package name has been changed from `SnapshotTesting` to `swift-snapshot-testing`, to better reflect community naming conventions (https://github.com/pointfreeco/swift-snapshot-testing/pull/555). This may require you to update any `Package.swift` files that depend on Snapshot Testing. - Support for CocoaPods and Carthage has been obsoleted. No new releases will be available on those platforms, starting with 1.10.0. Please use the Swift Package Manager to depend on Snapshot Testing. - Snapshot Testing now requires Swift 5.5+, as well at iOS 13+, macOS 10.15+, tvOS 13+, and watchOS 6+. ## Changes that may affect snapshot format/output > **Warning**: The following updates change how a strategy may output a snapshot, causing existing snapshot suites to fail. When upgrading, please rerecord your failing snapshots and audit the changes. - Fixed: A UIViewController strategy was not passing along the correct trait collection (thanks @arnopoulos, https://github.com/pointfreeco/swift-snapshot-testing/pull/554). - Fixed: iPhone XS Max portrait configuration was not applying base traits (thanks @imvm, https://github.com/pointfreeco/swift-snapshot-testing/pull/417) - Fixed: URLRequest strategy now sorts query items for more consistent diffing (thanks @mihai8804858, https://github.com/pointfreeco/swift-snapshot-testing/pull/491). - Removed: GLKView is no longer supported (thanks @jpsim, https://github.com/pointfreeco/swift-snapshot-testing/pull/507). ## Everything else - Added: Image-based strategies have a new `perceptualPrecision` option, which can be used to support snapshot tests across Intel and M1 devices. Along for the ride is a 90+% speed improvement to the strategies (thanks @ejensen, https://github.com/pointfreeco/swift-snapshot-testing/pull/628). - Added: Windows support, CI (thanks @MaxDesiatov, https://github.com/pointfreeco/swift-snapshot-testing/pull/532). - Added: Failure messages now include the snapshot name, if given (thanks @calda, https://github.com/pointfreeco/swift-snapshot-testing/pull/547). - Added: iPhone 13 configs (thanks @luispadron, https://github.com/pointfreeco/swift-snapshot-testing/pull/603). - Added: iPad 9.7" and iPad 10.2" configs (thanks @skols85, https://github.com/pointfreeco/swift-snapshot-testing/pull/405). - Added: iPhone 12 and iPhone 12 Pro Max configs(thanks @imvm, https://github.com/pointfreeco/swift-snapshot-testing/pull/418). - Added: `Snapshotting.json` for `Any` value (thanks @NachoSoto, https://github.com/pointfreeco/swift-snapshot-testing/pull/552). - Added: Newly-recorded snapshots are now attached to the test run (thanks @marcelofabri, https://github.com/pointfreeco/swift-snapshot-testing/pull/586). - Fixed: the UIImage strategy was using the device scale instead of the scale of the given images (thanks @codeman9, https://github.com/pointfreeco/swift-snapshot-testing/pull/472). - Fixed: the UIImage strategy now compares image contexts using the same colorspace (thanks @dflems, https://github.com/pointfreeco/swift-snapshot-testing/pull/446). - Fixed: the WebView strategy no longer overrides the delegate (thanks @teameh in https://github.com/pointfreeco/swift-snapshot-testing/pull/443). - Fixed: Patched a leak when running tests in a host application (thanks @llinardos, https://github.com/pointfreeco/swift-snapshot-testing/pull/511). - Fixed: False positive when asserting reference image with empty image (thanks @nuno-vieira, https://github.com/pointfreeco/swift-snapshot-testing/pull/453). - Fixed: watchOS compilation (thanks @aydegee, https://github.com/pointfreeco/swift-snapshot-testing/pull/579). - Fixed: Support for repeatedly running tests (thanks @krzysztofpawski, https://github.com/pointfreeco/swift-snapshot-testing/pull/585). - Infrastructure: Add `swift-snapshot-testing-stitch` to plugins list (thanks @Sherlouk, https://github.com/pointfreeco/swift-snapshot-testing/pull/483) - Infrastructure: Document diff tool configuration. - Infrastructure: README updates (thanks @MaatheusGois, @gohanlon), documentation fixes (thanks @heckj, @valeriyvan). - Infrastructure: Added GitHub issue templates (https://github.com/pointfreeco/swift-snapshot-testing/pull/556). - Infrastructure: Add SnapshotTestingHEIC to plugins list (thanks @alexey1312, https://github.com/pointfreeco/swift-snapshot-testing/pull/561). ## New Contributors * @arietis made their first contribution in https://github.com/pointfreeco/swift-snapshot-testing/pull/468 * @codeman9 made their first contribution in https://github.com/pointfreeco/swift-snapshot-testing/pull/472 * @Nikoloutsos made their first contribution in https://github.com/pointfreeco/swift-snapshot-testing/pull/482 * @mihai8804858 made their first contribution in https://github.com/pointfreeco/swift-snapshot-testing/pull/491 * @dflems made their first contribution in https://github.com/pointfreeco/swift-snapshot-testing/pull/446 * @skols85 made their first contribution in https://github.com/pointfreeco/swift-snapshot-testing/pull/405 * @imvm made their first contribution in https://github.com/pointfreeco/swift-snapshot-testing/pull/418 * @teameh made their first contribution in https://github.com/pointfreeco/swift-snapshot-testing/pull/443 * @MaatheusGois made their first contribution in https://github.com/pointfreeco/swift-snapshot-testing/pull/496 * @calda made their first contribution in https://github.com/pointfreeco/swift-snapshot-testing/pull/547 * @MaxDesiatov made their first contribution in https://github.com/pointfreeco/swift-snapshot-testing/pull/532 * @jpsim made their first contribution in https://github.com/pointfreeco/swift-snapshot-testing/pull/507 * @arnopoulos made their first contribution in https://github.com/pointfreeco/swift-snapshot-testing/pull/554 * @llinardos made their first contribution in https://github.com/pointfreeco/swift-snapshot-testing/pull/511 * @heckj made their first contribution in https://github.com/pointfreeco/swift-snapshot-testing/pull/601 * @aydegee made their first contribution in https://github.com/pointfreeco/swift-snapshot-testing/pull/579 * @valeriyvan made their first contribution in https://github.com/pointfreeco/swift-snapshot-testing/pull/630 * @ejensen made their first contribution in https://github.com/pointfreeco/swift-snapshot-testing/pull/628 * @luispadron made their first contribution in https://github.com/pointfreeco/swift-snapshot-testing/pull/603 * @alexey1312 made their first contribution in https://github.com/pointfreeco/swift-snapshot-testing/pull/561 * @gohanlon made their first contribution in https://github.com/pointfreeco/swift-snapshot-testing/pull/592 * @marcelofabri made their first contribution in https://github.com/pointfreeco/swift-snapshot-testing/pull/586 * @nuno-vieira made their first contribution in https://github.com/pointfreeco/swift-snapshot-testing/pull/453 * @krzysztofpawski made their first contribution in https://github.com/pointfreeco/swift-snapshot-testing/pull/585 **Full Changelog**: https://github.com/pointfreeco/swift-snapshot-testing/compare/1.9.0...1.10.0
1.9.0
1 year ago
- Added: publicized `data` snapshotting strategy (thanks @regexident). - Speed up `NSImage` comparison (thanks @finestructure, @JaapWijnen). - Fixed: enabled testing search paths (thanks @thedavidharris). - Infrastructure: links for AccessibilitySnapshot and AccessibilitySnapshotColorBlindness (thanks @Sherlouk).
1.8.2
2 years ago
- Rename `SnapshotTesting.record` to `SnapshotTesting.isRecording` to avoid clash with XCTestCase's new `record` method (thanks @xavierLowmiller). - Fix UIApplication selector to return the application as expected (thanks @mstultz). - Fix key window warning (thanks @tinder-maxwellelliott)
1.8.1
2 years ago
- Change minimum iOS version from iOS 10 to 11 to fix SwiftUI linking problems (thanks @thedavidharris).
1.8.0
2 years ago
- Added: SwiftUI support (thanks @natemann, @regexident). - Added: Apple TV 4K support (thanks @reez). - Added: Mac Catalyst support (thanks @rjchatfield). - Added: UIBezierPath, NSBezierPath, CGPath strategies (thanks @regexident). - Improved: don't crash on empty images, instead produce error artifact (thanks @mackoj). - Bug fixed: trait collection now passed to view controller's recursive description strategy (thanks @erikpoort). - Bug fixed: will no longer crash on hidden/unloaded web views (thanks @stuaustin). - Bug fixed: don't re-add view controller to window when already added (thanks @hassfers). - More test coverage (thanks @SatoTakeshiX, @sidepelican). - Typos fixed (thanks @freak4pc, @jstart). - Other improvements: timeout error messaging, installation instructions, troubleshooting instructions, Linux CI.
Xcode 11.4 Support
3 years ago
This release fixes a bug introduced in the Xcode 11.4 beta with SPM and Swift 5.2.
SwiftPM Tools 5.0 Support
3 years ago
This minor release introduces backwards compatibility for SwiftPM Tools @ 5.0.
1.7.0
3 years ago
### What's new? - New snapshot strategy: `wait` (#268) ### What's improved? - Performance improvement: don't diff during recording (#250) - Documentation improvement: Xcode 11 installation instructions (#256) - NSView rendering improvements (#260) - Documentation improvement: SPM test dependency instructions (#265) - cURL rendering improvements (#273) Thanks to @mr-v, @f-meloni, @schwmi, @freak4pc, and @ldstreet for contributing to this release!
1.6.0: Bug fixes and performance improvements πŸ˜†
3 years ago
### What's changed since last time? - Add device sizes for split view variants of iPads (#209) - Add recording to inline snapshotting (#212) - Sort cURL strategy headers (#214) - Add iOS minimum required deployment target to Package.swift (#215) - Allow dynamic size of views based on trait collection content sizes (#217) - Disable bitcode (#221) - Improve `_assertInlineSnapshot` ergonomics and tests (#231 and #232) - Use `URL.init(fileURLWithPath:isDirectory:)` to avoid file IO (#236) - Speed up image diffing (#248) - Improve image diff drawing performance (#249) Thanks to @Sherlouk, @crayment, @jayhickey, @MarianaMeireles, @pavel-y-ivanov, @ferranpujolcamins, @kirillyakimovich, and @mr-v for making this release happen!
iOS macOS tvOS
pointfreeco/isowords isowords-staging-deploy-v125
Open source game built in SwiftUI and the Composable Architecture.
⭐️ 2,114
πŸ•“ 26 weeks ago
iOS macOS watchOS tvOS
pointfreeco/swiftui-navigation 0.6.1
Tools for making SwiftUI navigation simpler, more ergonomic and more precise.
⭐️ 1,248
πŸ•“ 1 week ago
πŸ”– Release Notes

Releases

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.
0.6.1
1 week ago
## What's Changed * Made dependencies more explicit in both libraries, by @vincentisambart in https://github.com/pointfreeco/swiftui-navigation/pull/74 ## New Contributors * @vincentisambart made their first contribution in https://github.com/pointfreeco/swiftui-navigation/pull/74 **Full Changelog**: https://github.com/pointfreeco/swiftui-navigation/compare/0.6.0...0.6.1
0.6.0
2 weeks ago
## What's Changed * > **Warning**: The following is a breaking change. `ButtonState` action handlers, for alerts and confirmation dialogs, are now passed an _optional_ action, where `nil` represents dismissal from a button that has no action attached (https://github.com/pointfreeco/swiftui-navigation/pull/71). This allows you to get a callback when an alert is dismissed, which can be helpful for both domain-specific problems, but also for libraries built on top of SwiftUI Navigation, like [the Composable Architecture](https://github.com/pointfreeco/swift-composable-architecture). This means wherever you had an alert or confirmation dialog action handler, you must now handle an additional `nil` case: ```diff .alert(unwrapping: self.$destination, case: /Destination.alert) { action in switch action { case .randomize: self.count = .random(in: 0...1_000) case .reset: self.count = 0 + case nil: + break } } ``` * Added: `ConfirmationDialogState` now supports async action handlers (https://github.com/pointfreeco/swiftui-navigation/pull/68). > **Note**: async action handlers do not support implicit `ButtonStateAction` animations. If you perform async work in a button state action handler, you must perform any SwiftUI animations explicitly in the handler. * Fixed: Implicit `ButtonState` animations broke when action handlers became asynchronous. They have been restored for synchronous handlers, and will emit a runtime warning when an animation action is handled asynchronously (https://github.com/pointfreeco/swiftui-navigation/pull/70). * Infrastructure: doc fixes (thanks @dy-kim, https://github.com/pointfreeco/swiftui-navigation/pull/63; @Jager-yoo ,https://github.com/pointfreeco/swiftui-navigation/pull/64); Standups fixes (thanks @nesium, https://github.com/pointfreeco/swiftui-navigation/pull/66; https://github.com/pointfreeco/swiftui-navigation/pull/67) ## New Contributors * @dy-kim made their first contribution in https://github.com/pointfreeco/swiftui-navigation/pull/63 * @nesium made their first contribution in https://github.com/pointfreeco/swiftui-navigation/pull/66 **Full Changelog**: https://github.com/pointfreeco/swiftui-navigation/compare/0.5.0...0.6.0
0.5.0
4 weeks ago
## What's Changed * Changed: Alert actions can now be asynchronous (https://github.com/pointfreeco/swiftui-navigation/pull/61). * Infrastructure: New case study app showing off [swift-dependencies](https://github.com/pointfreeco/swift-dependencies) (https://github.com/pointfreeco/swiftui-navigation/pull/61). * Infrastructure: Typo fixes (thanks @Jager-yoo, https://github.com/pointfreeco/swiftui-navigation/pull/60; @john-flanagan, https://github.com/pointfreeco/swiftui-navigation/pull/62). * Fix typo by @john-flanagan in https://github.com/pointfreeco/swiftui-navigation/pull/62 ## New Contributors * @john-flanagan made their first contribution in https://github.com/pointfreeco/swiftui-navigation/pull/62 **Full Changelog**: https://github.com/pointfreeco/swiftui-navigation/compare/0.4.5...0.4.6
0.4.5
8 weeks ago
## What's Changed * Fixed regression: `Binding.case` can rewrite cases again (https://github.com/pointfreeco/swiftui-navigation/pull/54). **Full Changelog**: https://github.com/pointfreeco/swiftui-navigation/compare/0.4.4...0.4.5
0.4.4
8 weeks ago
## What's Changed * Fixed: `ButtonState.init` should not be ambiguous when `action` is omitted (https://github.com/pointfreeco/swiftui-navigation/pull/49). * Fixed: `SwiftUI.Alert.Button.init` is now passed an empty closure, not `nil`, when the action is omitted to prevent disabling the button on older platforms (iOS <15) (thanks @ski-u, https://github.com/pointfreeco/swiftui-navigation/pull/50). ## New Contributors * @ski-u made their first contribution in https://github.com/pointfreeco/swiftui-navigation/pull/50 **Full Changelog**: https://github.com/pointfreeco/swiftui-navigation/compare/0.4.3...0.4.4
0.4.3
9 weeks ago
## What's Changed * Fixed: macOS focus state synchronized with `View.bind` should now synchronize correctly (thanks @tgrapperon, https://github.com/pointfreeco/swiftui-navigation/pull/46). * Infrastructure: Confirmation dialog iPad/popover case study improvement (thanks @Jager-yoo, https://github.com/pointfreeco/swiftui-navigation/pull/38); README improvements (thanks @qmoya, https://github.com/pointfreeco/swiftui-navigation/pull/34); other case study improvements (thanks @Jager-yoo, https://github.com/pointfreeco/swiftui-navigation/pull/42); documentation typo fix (thanks @Shinolr, https://github.com/pointfreeco/swiftui-navigation/pull/43). ## New Contributors * @qmoya made their first contribution in https://github.com/pointfreeco/swiftui-navigation/pull/34 * @Shinolr made their first contribution in https://github.com/pointfreeco/swiftui-navigation/pull/43 * @tgrapperon made their first contribution in https://github.com/pointfreeco/swiftui-navigation/pull/46 **Full Changelog**: https://github.com/pointfreeco/swiftui-navigation/compare/0.4.2...0.4.3
0.4.2
11 weeks ago
## What's Changed * Exclude `id` from ButtonState's equatable conformance by @konomae in https://github.com/pointfreeco/swiftui-navigation/pull/33 ## New Contributors * @konomae made their first contribution in https://github.com/pointfreeco/swiftui-navigation/pull/33 **Full Changelog**: https://github.com/pointfreeco/swiftui-navigation/compare/0.4.1...0.4.2
0.4.1
11 weeks ago
## What's Changed * Some small fixes by @mbrandonw in https://github.com/pointfreeco/swiftui-navigation/pull/31 **Full Changelog**: https://github.com/pointfreeco/swiftui-navigation/compare/0.4.0...0.4.1
0.4.0
11 weeks ago
## What's Changed * Support navigation destinations, alerts, confirmation dialogs, and more! in https://github.com/pointfreeco/swiftui-navigation/pull/28. Read our [blog post][swiftui-nav-blog] for more information, and check out the [new documentation][swiftui-nav-docs]. * Fix typos in README and CaseStudies by @Jager-yoo in https://github.com/pointfreeco/swiftui-navigation/pull/30 ## New Contributors * @Jager-yoo made their first contribution in https://github.com/pointfreeco/swiftui-navigation/pull/30 **Full Changelog**: https://github.com/pointfreeco/swiftui-navigation/compare/0.3.0...0.4.0 [swiftui-nav-docs]: http://pointfreeco.github.io/swiftui-navigation/main/documentation/swiftuinavigation/ [swiftui-nav-blog]: http://pointfree.co/blog/posts/84-better-swiftui-navigation-apis
0.3.0
16 weeks ago
- Change: Swift tools version has been bumped to 5.5. - Change: `Switch` will now [runtime warn](https://www.pointfree.co/blog/posts/70-unobtrusive-runtime-warnings-for-libraries) instead of breakpoint when a case is left unhandled. - Change: `NavigationLink`'s `onNavigate` and `destination` closures have been flipped. The original order is now deprecated. - Change: Many APIs that required escaping closures no longer do.
iOS macOS watchOS tvOS
pointfreeco/swift-tagged 0.9.0
🏷 A wrapper type for safer, expressive code.
⭐️ 1,113
πŸ•“ 8 weeks ago
πŸ”– Release Notes

Releases

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.
0.9.0
8 weeks ago
## What's Changed ### `Tagged` * Add UUID helpers for `Tagged` (https://github.com/pointfreeco/swift-tagged/pull/63) * `Tagged.init()` for generating a tagged UUID * `Tagged.init(uuidString:)` for creating a tagged UUID from a UUID string ### `TaggedTime` * Add support for `Swift.Duration` (https://github.com/pointfreeco/swift-tagged/pull/62) **Full Changelog**: https://github.com/pointfreeco/swift-tagged/compare/0.8.0...0.9.0
0.8.0
12 weeks ago
## What's Changed * Add initializer without rawValue argument name. by @mbrandonw in https://github.com/pointfreeco/swift-tagged/pull/61 **Full Changelog**: https://github.com/pointfreeco/swift-tagged/compare/0.7.0...0.8.0
0.7.0
51 weeks ago
- Added: Conditional conformances to `ExpressibleByArrayLiteral` and `ExpressibleByDictionaryLiteral`. - Added: Conditional conformance to `Strideable` (thanks @TheOtherDave). - Added: Conditional conformance to `Sendable` (thanks @ericlewis). - Fixed: `Encodable` will now try to encode using the wrapped value's decoding initializer if the single value container fails to decode. - Infrastructure: Update README (thanks @volkdmitri, @mattyoung).
0.6.0
1 year ago
- Added: dynamic member lookup support for tagged values (thanks @Dragna). - Added: `ExpressibleByStringInterpolation` support (thanks @mdarnall). - Changed: SPM's package name has changed from `Tagged` to `swift-tagged` in the spirit of Apple conventions, and conventions set in other @pointfreeco packages). Migration strategy: remove any instances of `name: "Tagged"` from package files depending on Tagged).
Swift 5.1
3 years ago
### What's new? In Tagged: - Fix Date decoding with custom strategy (#24) - LocalizedError conformance (#33) - Identifiable protocol support (#35) - Add Collection and Sequence conditional conformances (#36) - Swift 5.1 support (#38) In TaggedTime: - Add DispatchTimeInterval methods to TaggedTime (#25) Thanks to @buscarini, @pteasima, @kaunamohammed, and @tonyarnold for contributing!
Swift 5
3 years ago
This release brings Tagged up to date with Swift 5!
Time, money, coerce
3 years ago
## What's new? - Added `TaggedTime` and `TaggedMoney` modules for safer time and safer money (#10). - Added `coerce` (#15). ## What's fixed? - Codability should now work on non-single value containers by delegating more directly to the underlying type (#12). - Fixed Carthage (#17).
New conformances, and map.
4 years ago
* Removed `ExpressibleByNilLiteral` conformance: https://github.com/pointfreeco/swift-tagged/pull/4 * Added `CustomPlaygroundDisplayConvertible` conformance: https://github.com/pointfreeco/swift-tagged/pull/5 * Added `map` to `Tagged`: https://github.com/pointfreeco/swift-tagged/pull/6 * Fixed deployment targets: https://github.com/pointfreeco/swift-tagged/pull/8
Announcing Tagged!
4 years ago
This preliminary release has the basic `Tagged` type implemented with a few starting conformances to common Swift protocols.
pointfreeco/swift-overture 0.5.0
🎼 A library for function composition.
⭐️ 1,093
πŸ•“ 1 week ago
πŸ”– Release Notes

Releases

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.
The Boring Swift 5 Release
3 years ago
### What's new? - Not much! We build for Swift 5 now!
0.4.0
3 years ago
## What's new * Add "combining" and "their" (#33) * Unzurry (#15) … * Add `update` (#39) ## What's fixed * Update to Swift 4.2 (#29) * Info.plist for targets (#35) * Make Overture app extensions friendly (#37) * Fix ambiguity with `with` and `mver` (#39)
Publicize `zip(with:)`s!
4 years ago
Thanks to https://github.com/pointfreeco/swift-overture/pull/26
Now with Zip
4 years ago
Overture 0.3.0 includes a handful of handy `zip` functions! This includes: - N-ary overloads of `zip` on sequences, zipping up to 10 sequences at once - `zip` on optionals, zipping up to 10 optionals at once - `zip(with:)` on both sequences _and_ optionals, for transforming zipped tuples into more interesting values See more about the announcement on our blog: [Overture: Now with Zip](https://www.pointfree.co/blog/ https://www.pointfree.co/blog/posts/15-overture-0-3-0-now-with-zip).
Now with Functional Setters
4 years ago
Overture 0.2.0! This release is all about setters: functions that allow us to build complex transformations out of smaller units. See more about the announcement on our blog: [Overture: Now with Functional Setters](https://www.pointfree.co/blog/posts/4-overture-now-with-functional-setters).
Function Composition without Operators
4 years ago
The first release of Overture! Overture is a function composition toolchain for Swift.
pointfreeco/swift-nonempty 0.4.0
🎁 A compile-time guarantee that a collection contains a value.
⭐️ 758
πŸ•“ 1 year ago
πŸ”– Release Notes

Releases

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.
0.4.0
1 year ago
- Bug fixed: `NonEmpty` now manages its own synthesized iterator in order to avoid potential stack overflows when calling to APIs on the iterator of the collection it wraps. - Changed: `NonEmpty` no longer conditionally conforms to `StringProtocol`. Apple documents against this conformance, and though engineers say there should be no issue with doing so, ABI-wise, we encountered a compiler crash when fixing the bug in the previous bullet point.
0.3.1
1 year ago
- Fixed: `+` operator between two `NonEmpty`s was ambiguous (thanks @buscarini).
0.3.0
1 year ago
- Changed: `NonEmpty` now wraps a base collection rather than a single element and collection as separate fields. This improves the performance and reliability of working with `NonEmpty` collections. This does unfortunately mean that invariants can compile and make their way into the system at run time, but we do our best to ensure they cannot be constructed. - Changed: the SPM package name has been changed from `NonEmpty` to `swift-nonempty` (thanks @maximkrouk). - Fixed: range subscripts no longer cause runtime stack overflows (thanks @clang13). - Removed: CocoaPods and Carthage support has been deprecated in favor of SPM.
0.2.2
2 years ago
- NonEmpty now correctly encodes and decodes structures as their more primitive collection types (#14)
0.2.1
3 years ago
### What's fixed: - Fix compiler error (#22) - Application extension support (#16, #18)
Swift 5
3 years ago
This release brings Swift 5 support, including an optimization around the mutation of non-empty collections!
Swift 4.2 Linux Edition
4 years ago
Swift 4.2 on Linux has a regression that prevents `NonEmpty` from conditionally conforming to `RandomAccessCollection`. We're temporarily removing support for the sake of compatibility.
Randomly Ready for Swift 4.2
4 years ago
This release updates NonEmpty to be compatible with Swift 4.2's randomness APIs.
Announcing NonEmpty!
4 years ago
This preliminary release has the basic `NonEmpty` type implemented with a few starting conformances to common Swift protocols.
pointfreeco/swift-parsing 0.11.0
A library for turning nebulous data into well-structured data, with a focus on composition, performance, generality, and ergonomics.
⭐️ 687
πŸ•“ 8 weeks ago
πŸ”– Release Notes

Releases

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.
0.11.0
8 weeks ago
## What's Changed - Swift 5.7 Updates (#261) - Changed: Parsing's builder limitations have been greatly improved. `OneOfBuilder` now takes an unlimited number of parsers, and `ParserBuilder` now takes an unlimited number of `Void` parsers, and up to 10 non-`Void` parsers. - Changed: Swift 5.7 Improvement: The `Parser`, `ParserPrinter`, `Conversion`, and `PrependableCollection` protocols now have primary associated types. - Added: `Formatted` parser-printer, for incrementally parsing and printing using Apple's family of formatters. - Changed: The `End` parser's conditional conformance requiring `Collection` has been broadened to work with any `Sequence` (thanks @JaapWijnen, #250). - Fixed: The `Prefix` parser-printer could erroneously fail to print when `max` was configured. This has been fixed (thanks @oskarek, #256). - Removed: The experimental `_URLRouting` module has been removed. Please upgrade to [the official package](https://github.com/pointfreeco/swift-url-routing), instead. - Infrastructure: Typo fixes (thanks @kamcma, #253; @elfenlaid, #257, #258). ## New Contributors * @kamcma made their first contribution in https://github.com/pointfreeco/swift-parsing/pull/253 * @elfenlaid made their first contribution in https://github.com/pointfreeco/swift-parsing/pull/257 **Full Changelog**: https://github.com/pointfreeco/swift-parsing/compare/0.10.0...0.11.0
0.10.0
32 weeks ago
- Added: `StartsWith`, `PrefixThrough`, and `PrefixUpTo` overloads to aid in type inference for substring and UTF-8 parsers (thanks @tgrapperon). - Changed: Parsing now has Apple platform requirements equivalent to SwiftUI (iOS 13+, macOS 10.15+, tvOS 13+, watchOS 6+). If these minimum requirements don't fit your needs, [let us know](https://github.com/pointfreeco/swift-parsing/discussions/new). - Fixed: `PipeEnd` now conforms to `ParserPrinter`, fixing printability of piped parsers (thanks @JaapWijnen). - Deprecated: the `_URLRouting` module is now deprecated. Use the [URL Routing](https://github.com/pointfreeco/swift-url-routing) package instead. - Removed: `Conversions.Parsing`, which was not reachable through any static member on `Conversion`, and confused some users. If you have a use case motivating this conversion, [let us know](https://github.com/pointfreeco/swift-parsing/discussions/new).
0.9.2
41 weeks ago
- Fixed: Added a missing `ParserPrinter` conformance to `OptionalOneOf`, which prevented parsers that used `if` statements in `@OneOfBuilder` blocks from being printers. The following changes have been made to the more experimental `_URLRouting` module: - Added: A `Body()` initializer that takes no arguments. It simply parses the entire body as `Data`. - Infrastructure: documentation changes.
0.9.1
42 weeks ago
- Fixed: A `Double.parser()` overflow bug has been fixed (thanks @tgrapperon). The following changes have been made to the more experimental `_URLRouting` module: - Added: A `URLRoutingClient` for wrapping a router and URL session into an HTTP client. - Fixed: A few potential bugs around `Field` and `Body` being empty.
0.9.0
43 weeks ago
Introduced the `ParserPrinter` protocol for invertible parsing.
0.8.0
47 weeks ago
- Added: A case-iterable, raw-representable parser. Simply tack `.parser()` onto any conforming type: ```swift enum Role: String, CaseIterable { case admin case guest case member } try Role.parser().parse("admin") // Role.admin ``` - Fixed: An Xcode 13.3 compiler error has been fixed. - Fixed: `Optionally` will now backtrack if the parser fails (thanks @randomeizer). - Fixed: `Double.parser()` now parses as freely as `Double.init`'s `LosslessStringConvertible` functionality. - Optimized: `Peek` and `Not` will only backtrack when they are successful (_i.e._, if `Peek`'s upstream parser successfully parses a value, or if `Not`'s upstream parser fails to parse a value). Backtracking on failure is now delegated to any upstream `OneOf`s. - Optimized: `OneOfMany` no longer backtracks its final failure, bringing it in line with the behavior of the variadic `OneOf`s. - Breaking change: The non-`inout` overloads of `Parser.parse` now attempt to fully consume `Collection`-based inputs. ```swift // Before: try Int.parser().parse("42hello") // 42 // After: try Int.parser().parse("42hello") // error: unexpected input // --> input:1:13 // 1 | 42hello // | ^ expected end of input ``` This change makes parsing a bit more strict by default in order to catch potential issues with input. If you want to ignore trailing output, use the `inout` version of `parse`, or explicitly describe how the input should be ignored in the parser, for example using `Optionally { Rest() }.map { _ in () }`. - Breaking change: The `Rest` parser now fails when the rest of input is empty. ```swift // Before: try Rest().parse("") // "" // After: try Rest().parse("") /// error: unexpected input /// --> input:1:1 /// 1 | /// | ^ expected a non-empty input ``` If your use of `Rest` should not fail on empty input, wrap it explicitly in an `Optionally` parser, or use `replaceError(with:)` to provide a default value of `""`. - Breaking change: `Peek` is now a `Void` parser. It can be used to inspect a value in order to test that a parser should be successful, but capturing any data is now the responsible for the parsers that comes afterward (thanks @randomeizer). - Breaking change: The `isSigned` parameter of `Int.parser()` has been removed. `Int.parser()` will now always parse a sign if `FixedWidthInteger.isSigned` returns true (_e.g._, `Int.parser()` will parse a sign, `UInt.parser()` will not.). If you want to parse a number without a sign, use a more explicit parser, or test for the sign before using `Int.parser()`. _E.g._: ```swift let digits = Prefix { $0.isNumber }.compactMap(Int.init) // ...or... let digits = Parse { Not { OneOf { "-"; "+" } } Int.parser() } ``` - Updated: `Double.parser()` can now be used on any type that conforms to `BinaryFloatingPoint`, including `Float16`. - Updated: `Many`'s `updateAccumulatingResult` can now throw. - Updated: Documentation has been revamped, including a new DocC-based static site with articles that cover common topics. - Infrastructure: Documentation fixes (thanks @haikusw).
0.7.1
50 weeks ago
- Improved: Error messages that occur at the same input range are now coalesced into a single error (thanks @mayoff). - Fixed: `Prefix` now eagerly consumes input. - Fixed: `Prefix` with a minimum length now throws an error at the correct input location, rather than the input location of that minimum length. - Infrastructure: README and documentation updates.
0.7.0
51 weeks ago
* Breaking change: `Parser.parse`'s method signature has changed from optional-returning to throwing: ```diff -func parse(_ input: inout Input) -> Output? +func parse(_ input: inout Input) throws -> Output ``` All of the parsers the library ships with now include error messages and context alongside failure, which can be printed: ```swift do { let output = users.parse(&input) } catch { print(error) } // error: multiple failures occurred // // error: unexpected input // --> input:3:11 // 3 | 3,Blob Jr,tru // | ^ expected "true" or "false" // // error: unexpected input // --> input:2:16 // 2 | 2,Blob Sr,false // | ^ expected end of input" ``` This is unfortunately a breaking change. It does not seem possible to support both throwing and optional-returning at the same time without requiring alternate breaking changes, so we opted for a clean break that requires upgrading existing parsers to throwing parsers. For most of our users, it will hopefully be a matter of prepending `try?` to lines that call `parse` to get things building again, though we hope folks will take full advantage of the new error messages. For users with custom parser conformances, they will need to do a little more work to make these parsers throwing. For more information about the release and migration strategies, see [our announcement](https://www.pointfree.co/blog/posts/73-parser-errors). * Added: `Parser.replaceError(with:)`, a parser modifier that transforms a throwing parser into a non-throwing parser by providing a default output. ```swift let sign = OneOf { "+".map { 1 } "-".map { -1 } } .replaceError(with: 1) var input = "-123"[...] // No `try` required: sign.parse(&input) // -1 input // "123" // Simply returns the default when parsing fails: sign.parse(&input) // 1 ``` * Added: the `Fail` parser has a new `.init(throwing:)` initializer that takes an `Error` for custom error messaging. * Deprecated: `Conditional` as a top-level parser has been deprecated. Use `if`-`else` builder syntax instead, which uses `Conditional` parsers under the hood, or reference the nested `Parsers.Conditional` type. * Infrastructure: documentation has been rewritten and expanded to reflect throwing parsers. * Infrastructure: Swift Package Index configuration was fixed so that our supported platform are better communicated (thanks @finestructure).
0.6.0
52 weeks ago
* Breaking change: many parsers that used to explicitly revert changes made to `input` when parsing fails (a process known as "backtracking") no longer do. See [our announcement](https://www.pointfree.co/blog/posts/72-backtracking-parsers) and pull request #108 for more information about the change and its motivation. `OneOf`, which previously did no backtracking whatsoever and trusted other parsers to do the work, is now the main entry point into backtracking behavior. Backtracking has been removed from `Double.parser()`, `Parser.filter`, `Parser.flatMap`, `Many` (with the exception of backtracking a trailing separator), `Parser.pipe`, `PrefixThrough`, and `PrefixUpTo`. Note: `Peek` and `Not` preserve their backtracking behavior, as they are designed to never consume any input. * Infrastructure: Add tests for `CharacterSet.parse` (thanks @andrewjl).
0.5.0
1 year ago
- Added: New result builder syntax for creating parsers! Use the `Parse` and `OneOf` entry points into `@ParserBuilder` and `@OneOfBuilder` blocks. - Added: A `Peek` parser: for running a parser and checking its result _without_ consuming input (thanks @randomeizer). - Added: A `Not` parser: for running a parser and succeeding if it fails (or failing if it succeeds) (thanks @randomeizer). - Changed: Many parsers have been updated to work with builder syntax, including `Skip`, `Many`, etc. - Changed: `Int.parser()` now takes an `Int` (not `Self`) as its radix. - Deprecated: Older, non-parser builder interfaces have been soft-deprecated. - Deprecated: Swift 5.3 support has been removed. - Performance: `Many`'s performance has been improved.
iOS macOS watchOS tvOS
pointfreeco/swift-dependencies 0.1.4
A dependency management library inspired by SwiftUI's "environment."
⭐️ 681
πŸ•“ 2 weeks ago
πŸ”– Release Notes

Releases

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.
0.1.4
2 weeks ago
## What's Changed * Fixed: Dependency values returning optionals no longer return `nil` instead of their default values (thanks @pyrtsa, https://github.com/pointfreeco/swift-dependencies/pull/29). * Fixed: If `liveValue` and `previewValue` are defined, a default `testValue` implementation will now properly invoke the `previewValue` and not the `liveValue` (https://github.com/pointfreeco/swift-dependencies/pull/30). * Infrastructure: Updated README with quick start usage (https://github.com/pointfreeco/swift-dependencies/pull/24) and documentation updates (thanks @oronbz, https://github.com/pointfreeco/swift-dependencies/pull/26, https://github.com/pointfreeco/swift-dependencies/pull/27, https://github.com/pointfreeco/swift-dependencies/pull/28). ## New Contributors * @oronbz made their first contribution in https://github.com/pointfreeco/swift-dependencies/pull/27 * @pyrtsa made their first contribution in https://github.com/pointfreeco/swift-dependencies/pull/29 **Full Changelog**: https://github.com/pointfreeco/swift-dependencies/compare/0.1.3...0.2.0
0.1.3
4 weeks ago
## What's Changed * Fixed: Don't setup observers in non-test contexts https://github.com/pointfreeco/swift-dependencies/pull/14 **Full Changelog**: https://github.com/pointfreeco/swift-dependencies/compare/0.1.2...0.1.3
0.1.2
4 weeks ago
## What's Changed * Fixed: Don't merge escaped dependencies with current task local value (thanks @tgrapperon, https://github.com/pointfreeco/swift-dependencies/pull/11). * Infrastructure: Documentation and README fixes and updates (thanks @tgrapperon, in https://github.com/pointfreeco/swift-dependencies/pull/6; https://github.com/pointfreeco/swift-dependencies/pull/8; https://github.com/pointfreeco/swift-dependencies/pull/9). ## New Contributors * @tgrapperon made their first contribution in https://github.com/pointfreeco/swift-dependencies/pull/6 **Full Changelog**: https://github.com/pointfreeco/swift-dependencies/compare/0.1.1...0.1.2
0.1.1
4 weeks ago
## What's Changed * Added: Swift 5.6 support (https://github.com/pointfreeco/swift-dependencies/pull/5). * Infrastructure: CI optimizations (https://github.com/pointfreeco/swift-dependencies/pull/1; https://github.com/pointfreeco/swift-dependencies/pull/4). **Full Changelog**: https://github.com/pointfreeco/swift-dependencies/compare/0.1.0...0.1.1
0.1.0
4 weeks ago
Initial release.
iOS macOS watchOS tvOS
pointfreeco/swift-case-paths 0.11.0
🧰 Case paths bring the power and ergonomics of key paths to enums!
⭐️ 664
πŸ•“ 5 weeks ago
πŸ”– Release Notes

Releases

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.
0.11.0
5 weeks ago
## What's Changed * Add XCTUnwrap(_:case:) test helper. https://github.com/pointfreeco/swift-case-paths/pull/95 **Full Changelog**: https://github.com/pointfreeco/swift-case-paths/compare/0.10.1...0.11.0
0.10.1
15 weeks ago
## What's Changed * Fixed: Added a workaround for a Swift bug in which single payload enums may not be extracted in release builds (#94). **Full Changelog**: https://github.com/pointfreeco/swift-case-paths/compare/0.10.0...0.10.1
0.10.0
16 weeks ago
## What's Changed * Added: `CasePath` now conforms to `Sendable` (https://github.com/pointfreeco/swift-case-paths/pull/90). Locking has been added around `embed`/`extract` functions, which should help avoid some data races without much overhead. If you notice any issues with the upgrade, please let us know! * Added: `CasePath.some`, for unwrapping optionals via `.some` or `/.some` instead of `/Optional.some` (https://github.com/pointfreeco/swift-case-paths/pull/91). **Full Changelog**: https://github.com/pointfreeco/swift-case-paths/compare/0.9.2...0.10.0
0.9.2
21 weeks ago
Fixed: The swift-case-paths package no longer publicly vends its internal schemes.
0.9.1
30 weeks ago
- Fixed: The `CasePath.init` overloads introduced in 0.9.0 now support the same implicit optional promotion behavior of `/`.
0.9.0
34 weeks ago
- Added: `CasePath.init(Enum.case)` alternative to `/Enum.case`. Xcode 14 beta 1 puts projects using Case Paths in a very broken state right now. This initializer is a workaround that can be used, instead, to avoid breaking things like syntax highlighting and file-wide indentation. - Fixed: case path composition operator associativity should now behave as expected (thanks @nonameplum).
0.8.1
41 weeks ago
- Bug fix: A Linux bug that could prevent multiple associated values from being extracted has been fixed.
0.8.0
1 year ago
- Changed: `CasePath.modify` now returns the value returned by its closure. - Fixed: runtime extraction of an `Error` existential should no longer crash (thanks @mayoff). - Fixed: runtime extraction of an object-bound protocol existential should no longer crash (thanks @iampatbrown). - Infrastructure: corrected README typos (thanks @ferologics) and example code, fixed CI and auto-format.
0.7.0
1 year ago
- Added: `CasePath.modify`, which allows you to mutate the associated value of an enum in-line: ```swift try (/Result<Int, Error>.success).modify(&result) { $0 *= 2 } ```
0.6.2
1 year ago
- Bug fixed: a regression in which case path expressions to enum cases with no associated values, where the `Root` is optional-promoted by the compiler, extraction wasn't working correctly.
iOS macOS watchOS tvOS
pointfreeco/swift-html 0.4.0
πŸ—Ί A Swift DSL for type-safe, extensible, and transformable HTML documents.
⭐️ 653
πŸ•“ 1 year ago
πŸ”– Release Notes

Releases

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.
0.4.0
1 year ago
- Added: Support for `viewport-fit` (thanks @hallee). - Added: Support for the `accept` attribute (thanks @xavierLowmiller). - Added: an experimental rendered for XML, `_xmlRender`. It is prefixed with an underscore for now. It renders valid XML and avoids rendering "void" (non-closing) HTML tags. - Changed: the package has been renamed to `swift-html` to match Apple conventions. - Fixed: `srcset` is now rendered in a stable order. - Removed: support for Carthage and CocoaPods. If you depend on these package managers, you must pin to an older version than 0.4.0.
0.3.1
3 years ago
This minor release restores support for Swift 4.2!
0.3.0
3 years ago
### What's new? - Swift 5 support (#51). - The element and attribute APIs have been completely revamped to use `static`s (#39). - The underlying `Node` API has been improved! - Arrays of nodes are now contained within a `.fragment` case, and `.element` has been updated to take a single child node, which may be a fragment (#23). - `Node` is now `ExpressibleByArrayLiteral` (#23). - `Node` is now `Equatable` and `Hashable` (#48). - `Node` now supports Swift 5 `ExpressibleByStringInterpolation` (#48). - The `mailto` API has been improved to take `subject` and other parameters (#41). - There's a new `template` tag helper (#43). The cumulative changes make for a big difference in API, but we think it's worth it! ``` diff -let link: Node = a([href("/")], ["Hello, ", .text(name), "!"]) +let link: Node = .a(attributes: [.href("/")], "Hello, \(name)!") ``` ### What's fixed? - Both `summary`/`details` and `fieldset`/`legend` have been fixed to compile correctly (#42). - The `HtmlSnapshotTesting` module has been fixed on Carthage by disabling bit-code (#49).
4 years ago
Fixed a typo where `onkeydown` was mistakenly rendered as `onkeyup`. https://github.com/pointfreeco/swift-html/pull/35
0.2.0
4 years ago
## What's new? - Support for Carthage and CocoaPods - A brand new module, `HtmlSnapshotTesting` for testing your HTML using [SnapshotTesting](https://github.com/pointfreeco/swift-snapshot-testing) - A new `debugRender` function, which renders HTML with human-readable indentation - Support for iOS, tvOS, and watchOS - Added a missing `style(unsafe:)` attribute helper that takes non-static strings - Added a missing `enctype` form attribute helper ## What's fixed? - Fixed `thead` and `tbody` element helpers to require nesting in a `table`
0.1.3
4 years ago
This release fixes how empty, non-void elements are closed.
0.1.2
4 years ago
0.1.1
4 years ago
0.1.0
4 years ago
Today we are open sourcing a new library for building HTML documents in Swift. It’s extensible, transformable, type-safe, and provides many benefits over templating languages. Read more [here](https://www.pointfree.co/blog/posts/16-open-sourcing-swift-html-a-type-safe-alternative-to-templating-languages-in-swift)!
iOS macOS tvOS linux macOS iOS
pointfreeco/swift-custom-dump 0.8.0
A collection of tools for debugging, diffing, and testing your application's data structures.
⭐️ 649
πŸ•“ 4 days ago
πŸ”– Release Notes

Releases

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.
0.8.0
5 days ago
- Changed: The dot-prefix abbreviation of enums introduced to dumps in in 0.7.0 has been extended to diffs (#72). - Changed: Single line string dumps will now use raw formatting when quotation marks or backslashes are detected (#72). > **Note**: These are breaking changes if you depend on a stable output format of Custom Dump. Consider updating code that depends on this formatting, or pin to an earlier release in the meantime.
0.7.0
1 week ago
## What's Changed * Changed: Nested enum output has changed to simulate dot-prefix abbreviation by omitting the type name (https://github.com/pointfreeco/swift-custom-dump/pull/71). > **Note**: This is a breaking change if you depend on the output format of Custom Dump. Consider updating code that depends on this formatting, or pin to an earlier release in the meantime. **Full Changelog**: https://github.com/pointfreeco/swift-custom-dump/compare/0.6.1...0.7.0
0.6.1
13 weeks ago
## What's Changed * Fixed: `KeyPath` release dumps on Darwin platforms should no longer crash (https://github.com/pointfreeco/swift-custom-dump/pull/68). * Fixed: `AnyHashable` dump has been improved (thanks @tahirmt, https://github.com/pointfreeco/swift-custom-dump/pull/64). * Infrastructure: Added `ObjectIdentifier` dump test (thanks @tahirmt, https://github.com/pointfreeco/swift-custom-dump/pull/66). **Full Changelog**: https://github.com/pointfreeco/swift-custom-dump/compare/0.6.0...0.6.1
0.6.0
18 weeks ago
- Added: Objects that are printed more than once per dump are now identified, _e.g._ `MyObject#1(…)` instead of `MyObject(…)` (thanks @tahirmt). - Fixed: Superclass fields are now correctly dumped alongside fields defined on the subclass (thanks @tahirmt).
0.5.2
21 weeks ago
* Add workaround for Xcode 14.1 beta 1, which fails to build iOS packages that import GameKit.
0.5.1
21 weeks ago
- Added: SwiftWASM support (thanks @inamiy). - Fixed: The swift-custom-dump package no longer publicly vends its internal schemes.
0.5.0
34 weeks ago
- Fixed: diffs now differentiate when value dumps the same output, but the type differs. ```swift let xs: [Any] = [Float(42)] let ys: [Any] = [Double(42)] diff(xs, ys) // [ // - [0]: 42 as Float // + [0]: 42 as Double // ] ```
0.4.0
41 weeks ago
## What's Changed * Update README.md by @iampatbrown in https://github.com/pointfreeco/swift-custom-dump/pull/34 * Remove platform requirements by @stephencelis in https://github.com/pointfreeco/swift-custom-dump/pull/37 * Run 13.2 CI on experimental build system by @stephencelis in https://github.com/pointfreeco/swift-custom-dump/pull/38 * Add CI labels by @stephencelis in https://github.com/pointfreeco/swift-custom-dump/pull/39 * Add issue templates and CoC by @stephencelis in https://github.com/pointfreeco/swift-custom-dump/pull/41 * Revert removal of platform requirements by @stephencelis in https://github.com/pointfreeco/swift-custom-dump/pull/42 * Show label for visited items by @brentleyjones in https://github.com/pointfreeco/swift-custom-dump/pull/43 * fix: Resolve Xcode 13 project startup beachball due to this playground by @importRyan in https://github.com/pointfreeco/swift-custom-dump/pull/46 ## New Contributors * @iampatbrown made their first contribution in https://github.com/pointfreeco/swift-custom-dump/pull/34 * @brentleyjones made their first contribution in https://github.com/pointfreeco/swift-custom-dump/pull/43 * @importRyan made their first contribution in https://github.com/pointfreeco/swift-custom-dump/pull/46 **Full Changelog**: https://github.com/pointfreeco/swift-custom-dump/compare/0.3.0...0.3.1
0.3.0
1 year ago
- Fixed: differences that were previously undetected in the dump are now better surfaced, _e.g._ when object identity differs, it will be printed in the diff. - Fixed: Xcode 13.2's new experimental build system is now supported (thanks @jaanussiim).
0.2.1
1 year ago
- Fixed: Null pointers no longer cause the dump function to crash, and are instead printed as `(null pointer)`
iOS macOS watchOS tvOS
pointfreeco/combine-schedulers 0.9.1
⏰ A few schedulers that make working with Combine more testable and more versatile.
⭐️ 558
πŸ•“ 14 weeks ago
πŸ”– Release Notes

Releases

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.
0.9.1
14 weeks ago
## What's Changed * Fixed: `TestScheduler.advance(to:) async` now runs on the main actor (#70). **Full Changelog**: https://github.com/pointfreeco/combine-schedulers/compare/0.9.0...0.9.1
0.9.0
14 weeks ago
## What's Changed * Swap implementations of advance(by/to:) by @mbrandonw in https://github.com/pointfreeco/combine-schedulers/pull/68 * Make UnimplementedScheduler behave like ImmediateScheduler. by @mbrandonw in https://github.com/pointfreeco/combine-schedulers/pull/69 **Full Changelog**: https://github.com/pointfreeco/combine-schedulers/compare/0.8.0...0.9.0
0.8.0
21 weeks ago
- Added: `AnySchedulerOf<UIScheduler>.shared` and `UIScheduler.test` endpoints have been added, making it friendlier to interact with UI schedulers in a testable way (thanks @emixb). - Fixed: The combine-schedulers package no longer publicly vends its internal schemes.
0.7.4
22 weeks ago
- Changed: The `TestScheduler` will now yield more time to the cooperative thread pool to better allow asynchronous work to be scheduled and picked up before assertions are run.
0.7.3
23 weeks ago
* Fixed: Combine Schedulers no longer causes DocC builds to fail in projects that depend on Combine Schedulers. This includes the Composable Architecture and applications/libraries that depend on the Composable Architecture. > **Warning**: This is a breaking change that may affect your application when upgrading. > > Prior to this update, Combine Schedulers automatically imported the Foundation framework alongside itself (due to an `@_exported import Foundation` declaration that was included in a file vendored from an Apple code base). > > Removing this has the following ramifications: > > * If you use [the Composable Architecture](https://github.com/pointfreeco/swift-composable-architecture) and are pinned to a version before [0.39.1](https://github.com/pointfreeco/swift-composable-architecture/releases/0.39.1), you must also explicitly pin Combine Schedulers to 0.7.2 or lower for previous versions of the Composable Architecture to build: > > ```swift > .package(url: "https://github.com/pointfreeco/combine-schedulers", .exact("0.7.2")), > ``` > > ...or you must update to the Composable Architecture 0.39.1 or higher. > > * If your application relied on ambient access to Foundation from importing Combine Schedulers (or the Composable Architecture), you must explicitly `import Foundation` in those files after upgrading, or you must pin Combine Schedulers to 0.7.2 or lower.
0.7.2
25 weeks ago
## What's Changed * Remove the SchedulerOf typealias. by @mbrandonw in https://github.com/pointfreeco/combine-schedulers/pull/64 This is needed due to the typealias causing Xcode editor stability problems. A Swift bug has been filed [here](https://github.com/apple/swift/issues/60550), and an Xcode feedback has been filed [here](https://gist.github.com/tgrapperon/977f0406f67c417a4730a8640ab50526). **Full Changelog**: https://github.com/pointfreeco/combine-schedulers/compare/0.7.1...0.7.2
0.7.1
25 weeks ago
- Added: Build support for non-Apple platforms. Allows libraries to depend on `CombineSchedulers` but still build for other platforms, like Linux.
0.7.0
26 weeks ago
- Added: `TestScheduler.advance(to:)`, for advancing to a specific moment in time (thanks @ytyubox). - Added: Async-friendly versions of `TestScheduler`'s `advance(by:)`, `advance(to:)`, and `run()` methods, which yield time to cooperative concurrency while scheduling work. - Added: Async-friendly functions for sleeping and running timers: `Scheduler.sleep(for:)` and `Scheduler.timer(interval:)`.
0.6.0
32 weeks ago
- Added: `AnySchedulerOf<DispatchQueue>.global(qos:)` (thanks @iampatbrown). - Renamed: `FailingScheduler` is now `UnimplementedScheduler`. Type aliases to `FailingScheduler` and `failing` statics are soft-deprecated and will become warnings in a future version of Combine Schedulers. - Infrastructure: README fix (thanks @junpluse).
0.5.3
1 year ago
* Updated xctest-dynamic-overlay to 0.2.1 (#42) (thanks @mRs- !)
iOS macOS watchOS tvOS
pointfreeco/swift-prelude 0.1.2
🎢 A collection of types and functions that enhance the Swift language.
⭐️ 429
πŸ•“ 4 weeks ago
πŸ”– Release Notes

Releases

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.
5 years ago
5 years ago
5 years ago
iOS macOS watchOS tvOS
pointfreeco/swift-validated 0.2.1
πŸ›‚ A result type that accumulates multiple errors.
⭐️ 381
πŸ•“ 1 week ago
πŸ”– Release Notes

Releases

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.
The NonEmpty Bugfix Edition
3 years ago
This locks Validated to NonEmpty 0.2.1, which fixes a compiler error from previous versions.
Swift 5 / NonEmpty 0.3 Support
3 years ago
This release supports Swift 5 and NonEmpty 0.3!
CocoaPods Consistency
4 years ago
This (very) minor update ensures that CocoaPods users can merely `import Validated`.
Swift 4.2 Linux Support
4 years ago
Validated relies on [NonEmpty](https://github.com/pointfreeco/swift-nonempty), which was affected by a regression in the release of Swift 4.2. This version of Validated updates this dependency in order to support Swift 4.2.
Release Validated
4 years ago
The first release of Validated: a result type that accumulates multiple errors.
pointfreeco/swift-identified-collections 0.6.0
A library of data structures for working with collections of identifiable elements in an ergonomic, performant way.
⭐️ 349
πŸ•“ 4 weeks ago
πŸ”– Release Notes

Releases

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.
0.6.0
4 weeks ago
## What's Changed * Fixed: Added `IdentifiedArray.subscript(position:) { set }` to fix SwiftUI editability (https://github.com/pointfreeco/swift-identified-collections/pull/48). * Infrastructure: Add DocC and GitHub Issue Templates (https://github.com/pointfreeco/swift-identified-collections/pull/47). **Full Changelog**: https://github.com/pointfreeco/swift-identified-collections/compare/0.5.0...0.6.0
0.5.0
12 weeks ago
## What's Changed * Added: `IdentifiedArray` now conforms to `Sendable`, `MutableCollection`, and `RangeReplaceableCollection` (#41). **Full Changelog**: https://github.com/pointfreeco/swift-identified-collections/compare/0.4.1...0.5.0
0.4.1
21 weeks ago
- Fixed: The swift-identified-collections package no longer publicly vends its internal schemes.
0.4.0
37 weeks ago
- Added: `IdentifiedArray.append(contentsOf:)`, which appends elements to an array iff they are not already present (thanks @jeffersonsetiawan). - Updated: `swift-collections` dependency has been updated to 1.0.2 (thanks @KaiOelfke). - Updated: Identified Collections platform requirements have been relaxed.
0.3.2
1 year ago
- Improved: performance of `IdentifiedArray.==` (thanks @mihaho).
0.3.1
1 year ago
- Fixed: Identified arrays that specify a key path should no longer fail equatable checks when elements are equal (thanks @sroche27r).
0.3.0
1 year ago
- Changed: Swift Identified Collections now depends on [Swift Collections 1.0.0](https://github.com/apple/swift-collections/releases/tag/1.0.0).
0.2.0
1 year ago
- Added: `IdentifiedArray.elements`, an array view of the identified array (thanks @p4checo). - Changed: `IdentifiedArray.move(fromOffsets:toOffset:)` and `IdentifiedArray.remove(atOffsets:)` no longer requires SwiftUI (thanks @gonzalolarralde). - Improved: `IdentifiedArray.move(fromOffsets:toOffset:)` and `IdentifiedArray.remove(atOffsets:)` are now much more performant. - Fixed: `IdentifiedArray.partition` now partitioning keys along with their values by calling down to the correct underlying implementation (thanks @tgt). - Fixed: stopped using a few APIs from Swift Collections that have been deprecated (thanks @diederich).
0.1.1
1 year ago
- Fixed: `removeLast(n:)` renamed to `removeLast(_:)` (thanks @konomae). - Fixed: dependence on Swift Collections relaxed to 0.0.1.
0.1.0
1 year ago
- Initial release! What are the main differences between this library and the `IdentifiedArray` [that shipped](https://github.com/pointfreeco/swift-composable-architecture/blob/0.20.0/Sources/ComposableArchitecture/SwiftUI/IdentifiedArray.swift) in [swift-composable-architecture 0.20.0](https://github.com/pointfreeco/swift-composable-architecture/releases/tag/0.20.0)? - It is now a wrapper around [`OrderedDictionary`](https://github.com/apple/swift-collections/blob/main/Documentation/OrderedDictionary.md) from [Swift Collections](https://github.com/apple/swift-collections). This means we can lean on the performance and correctness of Apple's library and avoid many of the bugs discovered in the original implementation. - It no longer conforms to `MutableCollection` and `RangeReplaceableCollection`. We take the same position Swift Collections [takes](https://github.com/apple/swift-collections/blob/main/Documentation/OrderedSet.md#sequence-and-collection-operations) with `OrderedSet` and `OrderedDictionary`. All elements in an identified array should have unique identity, operations such as `MutableCollection`'s subscript setter or `RangeReplaceableCollection`'s `replaceSubrange` assume the ability to insert/replace arbitrary elements in the collection, but allowing that could lead to duplicate values. Methods have been deprecated or made unavailable with suggested migration paths.
pointfreeco/swift-gen 0.4.0
🎱 Composable, transformable, controllable randomness.
⭐️ 255
πŸ•“ 39 weeks ago
πŸ”– Release Notes

Releases

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.
0.4.0
39 weeks ago
- Added: public APIs for `Xoshiro` generator (thanks @broomburgo). - Changed: the package name has changed from `Gen` to `swift-gen` for better SPM compatibility.
0.3.0
2 years ago
- Added: an implementation of the [xoshiro256**](http://prng.di.unimi.it) PRNG for seedable randomness. - Changed: the package name has been renamed from `Gen` to `swift-gen` to match the community and other Point-Free projects. - Deprecated: the LCRNG is not stable across Swift versions and thus has been deprecated. It will be obsoleted and removed in future releases. - Bug fixed: the `Float80` generator is now properly scoped to architectures that support it.
Swift 5!
3 years ago
### What's new? - Swift 5 support - A generator for the `Result` type
iOS Fix
3 years ago
Gen now correctly builds for iOS. https://github.com/pointfreeco/swift-gen/pull/6
Functional Randomness
3 years ago
Introducing Gen, a library for composable, transformable, controllable randomness!
pointfreeco/swift-url-routing 0.4.0
A bidirectional router with more type safety and less fuss.
⭐️ 250
πŸ•“ 13 weeks ago
πŸ”– Release Notes

Releases

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.
0.4.0
13 weeks ago
## What's Changed - Fixed: Fields (query, headers, form data, etc.) now preserve order when printed (thanks @fonkadelic, #57). To preserve this order, URL Routing now depends on Apple's [Swift Collections](https://github.com/apple/swift-collections) package. - Fixed: Updated calls to `withTaskCancellation` to the non-deprecated version (thanks @kgrigsby59, #56). ## New Contributors * @kgrigsby59 made their first contribution in https://github.com/pointfreeco/swift-url-routing/pull/56 **Full Changelog**: https://github.com/pointfreeco/swift-url-routing/compare/0.3.1...0.4.0
0.3.1
20 weeks ago
* Fixed: [A regression](https://github.com/apple/swift/issues/61192) introduced to Swift in Xcode 14.1 broke compilation. This release includes a workaround to get things building again.
0.3.0
32 weeks ago
- Added: `Fragment` parser, for parsing a URL fragment (thanks @ryanbooker). - Added: `Host` parser, for parsing a URL host (thanks @ryanbooker). - Changed: URL Routing's platform requirements have been bumped to match Parsing's requirements, equivalent to SwiftUI (iOS 13+, macOS 10.15+, tvOS 13+, watchOS 6+). If these minimum requirements don't fit your needs, [let us know](https://github.com/pointfreeco/swift-url-routing/discussions/new). - Infrastructure: Fixed documentation typos (thanks @fonkadelic, @volkdmitri).
0.2.0
37 weeks ago
- Added: `URLRoutingClient` can now be configured with a JSONDecoder for global response decoding (thanks @jtouzy). - Added: a `Scheme` router (thanks @ryanbooker). - Added: `URLRoutingClient.data(for:)`. - Updated: `URLRoutingClient.request(_:as:decoder:)` has been renamed to `URLRoutingClient.decodedResponse(for:as:decoder:)`. - Changed: the package name has been changed to `swift-url-routing` to match its repo name. - Optimized: added inlining to the path component router. - Infrastructure: documentation updates. - Infrastructure: added SPI badges to README (thanks @finestructure).
0.1.0
40 weeks ago
Our first release!
iOS macOS watchOS tvOS
pointfreeco/swift-enum-properties 0.1.0
🀝 Struct and enum data access in harmony.
⭐️ 200
πŸ•“ 1 year ago
πŸ”– Release Notes

Releases

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.
Hello, enums!
3 years ago
This is the first release of `generate-enum-properties`, which makes working with Swift enums like working with Swift structs!
pointfreeco/swift-clocks 0.2.0
⏰ A few clocks that make working with Swift concurrency more testable and more versatile.
⭐️ 146
πŸ•“ 13 weeks ago
πŸ”– Release Notes

Releases

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.
0.2.0
13 weeks ago
## What's Changed - Added: A concrete type-eraser, `AnyClock`, that can be used to erase clocks in positions where existentials cannot be automatically opened, _.e.g._ in Async Algorithms' `timer`, `debounce`, and `throttle` operations. **Full Changelog**: https://github.com/pointfreeco/swift-clocks/compare/0.1.4...0.2.0
0.1.4
15 weeks ago
## What's Changed * Added: macCatalyst support (#6). **Full Changelog**: https://github.com/pointfreeco/swift-clocks/compare/0.1.3...0.1.4
0.1.3
15 weeks ago
## What's Changed * Fixed: macOS, tvOS, watchOS platforms are now supported. **Full Changelog**: https://github.com/pointfreeco/swift-clocks/compare/0.1.2...0.1.3
0.1.2
15 weeks ago
## What's Changed * Fixed: `TestClock.run` will now cancel any suspensions when its timeout expires (#3). * Removed: SPM schemes are no longer checked in and will not show up by default when depending on swift-clocks (#4). * Infrastructure: add Linux CI (#3); add issue templates / CoC (#4). **Full Changelog**: https://github.com/pointfreeco/swift-clocks/compare/0.1.1...0.1.2
15 weeks ago
* Fixed: Xcode's SPM integration does not allow for unsafe build flags to be configured for version-based releases. We've removed the build settings to fix this.
0.1.0
15 weeks ago
⏰ A few clocks that make working with Swift concurrency more testable and more versatile.
iOS macOS watchOS tvOS
pointfreeco/xctest-dynamic-overlay 0.8.2
Define XCTest assertion helpers directly in your application and library code.
⭐️ 134
πŸ•“ 2 days ago
πŸ”– Release Notes

Releases

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.
0.8.2
2 days ago
## What's Changed * Added: `XCTFail` now detects when it's called from a host application, outside a test case stack and generates an appropriate warning (thanks @tgrapperon, https://github.com/pointfreeco/xctest-dynamic-overlay/pull/48). This can help folks diagnose when test helpers are called from their app targets and cause unrelated failures. ## New Contributors * @tgrapperon made their first contribution in https://github.com/pointfreeco/xctest-dynamic-overlay/pull/48 **Full Changelog**: https://github.com/pointfreeco/xctest-dynamic-overlay/compare/0.8.1...0.8.2
0.8.1
4 weeks ago
## What's Changed * Fixed: Mark `XCTFail` as `@_disfavoredOverload` to avoid ambiguity when XCTest is imported (thanks @davdroman, https://github.com/pointfreeco/xctest-dynamic-overlay/pull/46). ## New Contributors * @davdroman made their first contribution in https://github.com/pointfreeco/xctest-dynamic-overlay/pull/46 **Full Changelog**: https://github.com/pointfreeco/xctest-dynamic-overlay/compare/0.8.0...0.8.1
0.8.0
5 weeks ago
## What's Changed * Added: New overloads of `unimplemented` that return values instead of closures. These can be invoked directly in initializers that take autoclosures instead of closures (#41). * Added: `XCTCurrentTestCase` is now publicly available under `@_spi(CurrentTestCase)` (#42). * Infrastructure: Fixed docs to use `unimplemented` rather than `XCTUnimplemented` (thanks @hmhv #40). ## New Contributors * @hmhv made their first contribution in https://github.com/pointfreeco/xctest-dynamic-overlay/pull/40 **Full Changelog**: https://github.com/pointfreeco/xctest-dynamic-overlay/compare/0.7.0...0.8.0
0.7.0
7 weeks ago
## What's Changed * Support more generated placeholder types (thanks @iampatbrown, https://github.com/pointfreeco/xctest-dynamic-overlay/pull/39). ## New Contributors * @iampatbrown made their first contribution in https://github.com/pointfreeco/xctest-dynamic-overlay/pull/39 **Full Changelog**: https://github.com/pointfreeco/xctest-dynamic-overlay/compare/0.6.0...0.7.0
0.6.0
12 weeks ago
## What's Changed * Added: File/line context is now printed in `unimplemented` failure messages (#36). * Fixed: `unimplemented` failures now print the debug description of any arguments. * Fixed: Added resilience around detecting the current XCTest case. **Full Changelog**: https://github.com/pointfreeco/xctest-dynamic-overlay/compare/0.5.0...0.6.0
0.5.0
16 weeks ago
- Changed: `XCTUnimplemented` has been renamed `unimplemented`. (`XCTUnimplemented` is soft-deprecated and will become hard-deprecated in a future release.) - Changed: Runtime warnings emitted by `XCTFail` outside of tests now emit the original failure message unchanged.
0.4.1
21 weeks ago
- Fixed: XCTestDynamicOverlay now builds for SwiftWASM environments (thanks @inamiy).
0.4.0
26 weeks ago
- Changed: `XCTUnimplemented` is now overloaded to take a non-optional `placeholder`, or nothing at all, to prevent ambiguity in situations where you pass a `.none` value.
0.3.3
30 weeks ago
- Fixed: Linux now builds correctly when statically linking against the standard library. - Infrastructure: Cleaned up DocC.
0.3.2
31 weeks ago
- Changed: `XCTUnimplemented` errors now print more context, including the values passed to the function. - Fixed: the underscored `_XCTIsTesting` property no longer returns `false` when tests run in app hosts.
iOS macOS watchOS tvOS
pointfreeco/vapor-routing 0.1.3
A bidirectional Vapor router with more type safety and less fuss.
⭐️ 74
πŸ•“ 2 days ago
πŸ”– Release Notes

Releases

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.
0.1.3
2 days ago
## What's Changed * Fixed: Large request bodies no longer fail to parse when fed in as streaming input (https://github.com/pointfreeco/vapor-routing/pull/23). **Full Changelog**: https://github.com/pointfreeco/vapor-routing/compare/0.1.2...0.1.3
0.1.2
13 weeks ago
- Fixed: A compatibility issue with [URL Routing](https://github.com/pointfreeco/swift-url-routing) 0.4.0 has been fixed.
0.1.1
37 weeks ago
- Fixed: Errors thrown in the handler should now correctly propagate in Vapor applications as expected. - Infrastructure: README updates and fixes (thanks @gohanlon, @finestructure)
0.1.0
40 weeks ago
Our first release!
macOS linux macOS iOS
pointfreeco/composable-core-location 0.2.0
A library that bridges the Composable Architecture and Core Location.
⭐️ 73
πŸ•“ 46 weeks ago
πŸ”– Release Notes

Releases

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.
0.2.0
46 weeks ago
> Note: This release is breaking! The APIs have changed significantly. - Breaking change: Clients have been simplified so that endpoints no longer require ids. This means the client lifecycle is now internal to the live instance and managing explicitly via `create` and `destroy` is no longer necessary. As such, `create` was also renamed to `delegate`. - Changed: Pinned to TCA 0.27.1 (for failing effects) (thanks @andreyz). - Added: Monitor significant changes API (thanks @joeblau). - Added: `requestTemporaryFullAccuracyAuthorization` (thanks @tomhut). - Fixed: Publicized initializers for `Region` (thanks @ferologics). - Fixed: Preserve `Visit`'s `CLVisit` raw value (thanks @andreyz). - Fixed: `requestLocationWhileInUse` is now available on macOS (thanks @fire-at-will). - Infrastructure: README fixes (thanks @hanneskaeufler).
0.1.0
2 years ago
First release since being extracted from https://github.com/pointfreeco/swift-composable-architecture - Added: support for headings APIs (thanks @dannyhertz). - Added: support for accuracy authorization (thanks @mackoj).
iOS macOS watchOS tvOS
pointfreeco/swift-html-vapor 0.4.0
πŸ’§ Vapor plugin for type-safe, transformable HTML views.
⭐️ 69
πŸ•“ 1 year ago
πŸ”– Release Notes

Releases

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.
0.4.0
1 year ago
- Updated: Vapor 4 support (thanks @JaapWijnen) - Updated: swift-html 0.4.0 support
0.3.1
3 years ago
Synchronizes the Swift 4.2-compatible release of swift-html 0.3.1.
0.3.0
3 years ago
This release brings in support for Html 0.3.0 and Swift 5!
0.1.0
4 years ago
macOS linux macOS iOS
pointfreeco/composable-core-motion 0.1.1
A library that bridges the Composable Architecture and Core Motion.
⭐️ 22
πŸ•“ 1 year ago
πŸ”– Release Notes

Releases

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.
0.1.1
1 year ago
- Fixed: removed broken protocol conformance (thanks @andreyz). - Fixed: corrected README typo (thanks @barksten).
0.1.0
2 years ago
First release since being extracted from https://github.com/pointfreeco/swift-composable-architecture - Added: support for headphone motion manager.
iOS macOS watchOS
pointfreeco/swift-html-kitura 0.3.0
☁️ Kitura plugin for type-safe, transformable HTML views.
⭐️ 13
πŸ•“ 1 year ago
πŸ”– Release Notes

Releases

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.
Html 0.3.0 / Swift 5 Support
3 years ago
This release brings in support for Html 0.3.0 and Swift 5!
First Release!
4 years ago
linux macOS iOS

Swiftpack is being maintained by Petr Pavlik | @ptrpavlik | @swiftpackco | API | Analytics