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.38.1
A library for building applications in a consistent and understandable way, with composition, testing, and ergonomics in mind.
⭐️ 6,371
πŸ•“ 7 hours 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.38.1
10 hours ago
- Fixed: 0.38.0 introduced a regression that could cause test stores that receive `BindingAction`s from effects to cause test failures. This has been fixed.
0.38.0
17 hours ago
- Added: A new runtime warning for when a `BindingAction` is sent to the store but `Reducer.binding()` wasn't applied to the reducer. This should help diagnose missing integrations faster. - Fixed: A regression for `TestStore.send` and `receive` was introduced in 0.37.0 that failed to perform assertions against state when the trailing closure was omitted. This has been fixed (thanks @umbertovolta).
0.37.0
4 days ago
- Added: `Effect.animation()`, which adds animation to an effect without the need of a scheduler. - Changed: `TestStore` state modification failures are less noisy. - Renamed: `ViewStore.suspend(while:)` has been renamed to `ViewStore.yield(while:)`. - Bug fixed: A bug was introduced to the deprecated `TestStore.assert` APIs in 0.36.0, which caused test failures when a sent/received test action left state unchanged. This has been fixed. - Infrastructure: Worked around a SwiftUI bug/warning in the Case Studies demo; cleaned up some of the library's generic signatures.
0.36.0
3 weeks ago
- Added: `Effect.throttle` overloads that take `Any.Type` (thanks @elkraneo). - Added: `TestStore.state`, which reflects the state of the store between assertions. This property can be used to further probe test store state over time and make additional assertions. - Updated: `WithViewStore` can be in more places, like `@CommandsBuilder` (thanks @tgrapperon). - Fixed: `Effect.task` modifiers now deliver output and completion on the main actor, avoiding potential data races. - Documentation: Added support for [SPI documentation](https://blog.swiftpackageindex.com/posts/auto-generating-auto-hosting-and-auto-updating-docc-documentation/) (thanks @finestructure). - Infrastructure: typo fixes (thanks @konomae) and demo app cleanup.
0.35.0
5 weeks ago
- Breaking change: test stores will now catch assertions that do not change state (thanks @rcarver). ```swift // Before: store.send(.actionThatDoesntChangeState) { $0.state = .sameStateAsBefore } // βœ… // After: store.send(.actionThatDoesntChangeState) { $0.state = .sameStateAsBefore } // ❌ Expected to modify the expected state, but no change occurred. ``` To fix, remove the trailing closure assertion to let the test store know you don't expect its state to change: ```swift store.send(.actionThatDoesntChangeState) // βœ… ``` - Added: Effect cancellation endpoints can now take types as identifiers, a slightly simpler alternative to safely defining and instantiating a hashable type: ```swift // Before: struct CancelId: Hashable {} return .cancel(id: CancelId()) // After: enum CancelId {} return .cancel(id: CancelId.self) ``` - Added: A new overload of `eraseToEffect` that takes a transform function. This provides symmetry to `catchToEffect` and can help streamline effect work in the reducer (thanks @klundberg). ```swift // Before: return environment.doSomething() .map(Action.case) .eraseToEffect() // After: return environment.doSomething() .eraseToEffect(Action.case) ``` - Added: A new overload of `Effect.fireAndForget` that takes an async, throwing function. ```swift return .fireAndForget { try await environment.analytics(event: .tappedProfile) } ``` - Changed: The synchronous version of `Effect.fireAndForget` can now `throw`, which will simply terminate the effect's execution early if an error is thrown. - Changed: Runtime warnings should now show up closer to the source of the warning (thanks @iampatbrown). - Changed: When multiple `TestStore` failure messages stack, they should print in a better, more readable order. - Changed: Case Paths has been pinned to a newer version (thanks @nsillik). - Fixed: A bug in which the array-based overload of `Effect.cancel(ids:)` was not being favored over the variadic overload would treat the entire array as the cancel token and not each individual item has been fixed (thanks @iampatbrown). - Fixed: A few small warnings that show up in Swift 5.7 have been fixed. - Performance: Effect cancellation lookup has been improved for type-safe identifiers. - Infrastructure: Fixed SPI's config file (thanks @finestructure). - Infrastructure: The long-living effect SwiftUI case study has been modernized and simplified.
0.34.0
14 weeks ago
- Changed: An effect is now not considered "in-flight" till it is kicked off. This fixes a potential behavior where marking a timer effect cancellable (which is already cancellable by default) could prevent the effect from running. - Changed: Runtime warnings now emit XCTest failures, as well, making it easier to catch common issues in your tests. - Optimized: In-flight effects are now cancelled inline (thanks @iampatbrown). - Fixed: `Effect.cancel(ids:)` now properly routes to the sequence overload (thanks @iampatbrown). - Fixed: `WithViewStore` no longer breaks in certain contexts, _e.g._ when placed inside a `GeometryReader` (thanks @tgrapperon). - Infrastructure: Added Arabic translation to README (thanks @NorhanBoghdadi). - Infrastructure: Added Simplified Chinese translation to README (thanks @sh3l6orrr). - Infrastructure: Cleaned up case studies (thanks @rono23). - Infrastructure: Fixed and added unit tests to UIKit list case study (thanks @bjford). - Infrastructure: Fixed a few missing asset warnings in demo applications (thanks @tgrapperon).
0.33.1
23 weeks ago
- Bug fixed: the new runtime warning system no longer crash iOS 13 debug builds (thanks @mcfans). - Infrastructure: modernized demo apps by removing scene delegates and unneeded Info.plists.
0.33.0
24 weeks ago
- Bug fixed: nested calls to `Effect.cancellable` no longer prevent certain outputs from being emitted (thanks @iampatbrown). Breaking change: a consequence of this fix is that `Effect.timer`s running on an immediate scheduler will now immediately emit its first output in tests. If a test fails after upgrading to this version, you may need to assert against the output of such an effect.
0.32.0
24 weeks ago
- Changed: operators like `Reducer.optional()` and `Reducer.forEach()` no longer halt with a breakpoint. Instead, issues are logged via Xcode's runtime warning system.
0.31.0
26 weeks ago
- Changed: Upstream dependency requirements have been bumped to bring in bug fixes. - Changed: Concurrency tools now require Xcode 13.2 or greater. - Fixed: Worked around an iOS 14 SwiftUI availability check crash affecting the `.alert` and `.confirmationDialog` view modifiers. - Infrastructure: Simplified test store internals, fixed demo deprecation warnings
iOS macOS watchOS tvOS
pointfreeco/swift-snapshot-testing 1.9.0
πŸ“Έ Delightful Swift snapshot testing.
⭐️ 2,659
πŸ•“ 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.
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
1 year 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
2 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
2 years ago
This minor release introduces backwards compatibility for SwiftPM Tools @ 5.0.
1.7.0
2 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 πŸ˜†
2 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!
Inline snapshots and more strategies
3 years ago
### What's new * @rjchatfield has introduced (#199) a brand new way of snapshotting textual information, called "inline snapshot testing," which automatically inlines snapshots directly in your test file. The 1.5.0 release includes a preview of this functionality! You can use the `_assertInlineSnapshot` helper to try it out. Thanks to @rjchatfield for the PR, and find out more [here](https://medium.com/@rjchatfield/inline-snapshot-testing-e5e237fc47f3). ![](https://user-images.githubusercontent.com/5361118/54913569-2693bf00-4f47-11e9-9733-ec6b5ff17ea2.gif) * Two new `URLRequest` snapshot strategies have been included. First, @Sherlouk has included a `curl` snapshotting strategy (#203), which snapshots your prepared requests in the cURL format. Also we now have a snapshot strategy for capturing a `URLRequest` with its body pretty printed, when possible (#157). This helps make `POST` requests more easily inspectable in the reference file.
Swift 5 Support
3 years ago
This release brings SnapshotTesting up to date with Swift 5! ### What's changed? - Swift 5 support! - The `SnapshotTestCase` subclass is no longer needed on Linux and has been deprecated as a type alias to `XCTestCase`. The type alias will be removed in a future version (#200). - The `dump` strategy has been optimized (#195).
iOS macOS tvOS
pointfreeco/isowords isowords-staging-deploy-v123
Open source game built in SwiftUI and the Composable Architecture.
⭐️ 1,791
πŸ•“ 37 weeks ago
iOS macOS
pointfreeco/swift-overture 0.5.0
🎼 A library for function composition.
⭐️ 1,059
πŸ•“ 35 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.
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!
3 years ago
Thanks to https://github.com/pointfreeco/swift-overture/pull/26
Now with Zip
3 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-tagged 0.7.0
🏷 A wrapper type for safer, expressive code.
⭐️ 992
πŸ•“ 18 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.7.0
18 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
2 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/swiftui-navigation 0.1.0
Tools for making SwiftUI navigation simpler, more ergonomic and more precise.
⭐️ 866
πŸ•“ 31 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.0
31 weeks ago
- Initial release.
iOS macOS watchOS tvOS
pointfreeco/swift-nonempty 0.4.0
🎁 A compile-time guarantee that a collection contains a value.
⭐️ 711
πŸ•“ 45 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
45 weeks 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
2 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
3 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
3 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-html 0.4.0
πŸ—Ί A Swift DSL for type-safe, extensible, and transformable HTML documents.
⭐️ 618
πŸ•“ 44 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
44 weeks 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).
3 years ago
Fixed a typo where `onkeydown` was mistakenly rendered as `onkeyup`. https://github.com/pointfreeco/swift-html/pull/35
0.2.0
3 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
3 years ago
This release fixes how empty, non-void elements are closed.
0.1.2
3 years ago
0.1.1
3 years ago
0.1.0
3 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)!
linux macOS iOS
pointfreeco/swift-parsing 0.9.2
A library for turning nebulous data into well-structured data, with a focus on composition, performance, generality, and ergonomics.
⭐️ 589
πŸ•“ 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.2
8 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
9 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
10 weeks ago
Introduced the `ParserPrinter` protocol for invertible parsing.
0.8.0
15 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
18 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
18 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
19 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
21 weeks 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.
0.4.1
24 weeks ago
- Changed: `Many` and `OptionalParser`'s `Upstream` generic has been deprecated and renamed to `Element` and `Wrapped`. - Infrastructure: benchmarks and documentation cleanup.
0.4.0
28 weeks ago
- Added: initializer overloads of `Prefix` and other parsers that aid in type inference. _E.g._, the following now type-checks: ```swift Prefix { $0 == " " } // Inferred to be "Prefix<Substring>" Prefix { $0 == .init(ascii: " ") } // Inferred to be "Prefix<Substring.UTF8View>" ``` - Added: `CharacterSet` now conforms to `Parser`. - Changed: `Many` will now trigger a warning breakpoint when its upstream parser succeeds but fails to consume any data, which can cause an infinite loop. - Fixed: `Double.parser()` exponent parsing (thanks @bradhowes) and general `Double` parsing edge cases. - Infrastructure: documentation fixes (thanks @igor1309). - Infrastructure: improved "arithmetic" demo parser to use more ergonomic/performant `InfixOperator` parser. - Infrastructure: benchmarks now better reflect typical parsing (substring UTF8 views vs. unsafe buffer pointers).
pointfreeco/swift-case-paths 0.9.0
🧰 Case paths bring the power and ergonomics of key paths to enums!
⭐️ 564
πŸ•“ 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.9.0
2 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
9 weeks ago
- Bug fix: A Linux bug that could prevent multiple associated values from being extracted has been fixed.
0.8.0
24 weeks 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
47 weeks 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
47 weeks 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.
0.6.1
48 weeks ago
- Bug fixed: failed extractions via the optional demotion handled in [0.6.0](https://github.com/pointfreeco/swift-case-paths/releases/0.6.0) would infinitely recurse.
0.6.0
48 weeks ago
- Fixed regression: Swift can optional-promote the `Root` of an embed function `(Value) -> Root` to `(Value) -> Root?` and yield `CasePath<Root?, Value>` instead of `CasePath<Root, Value>. Extraction was still handled successfully in 0.3.0 and earlier, but broke in 0.4.0. Thanks @mayoff for the fix! - Fixed regression: Swift can optional-demote the `Value` of an embed function `(Value?) -> Root` to `(Value) -> Root` and yield `CasePath<Root, Value>` instead of `CasePath<Root, Value?>. Extraction was still handled successfully in 0.3.0 and earlier, but broke in 0.4.0. Thanks @mayoff for this fix as well! - A family of helpers functions around reflection/runtime extraction has been deprecated, this includes module-level `extract` functions and `CasePath.case`. The library now always favors using case path syntax (`/Root.caseName`) or the `CasePath.extract(from:)` method.
0.5.0
49 weeks ago
- Reflection code is now 100% powered by the runtime metadata and no longer relies on `Mirror`! Thanks @mayoff for diving _even deeper_ into the problem, surfacing with a nice and succinct solution.
0.4.0
50 weeks ago
- Reflection code has been further improved to use the Swift runtime for repeat successful extractions after the first successful one. This kind of extraction is about 25x faster than the previous release, and 50x faster than the release before it. Thanks, @mayoff!
0.3.0
50 weeks ago
- Reflection code has been rewritten for improved performance and simplicity. Successful extractions perform a little over 2Γ— faster than previously. Failed extractions, at worst, perform 2Γ— faster, and at best, perform in under 100ns (best case assumes the case path has made a successful extraction at some point of the application's lifetime). Note: some of these changes are breaking (see #32 for more details and upgrade paths), but should not affect most users of the library. - `CasePath` now conforms to `CustomStringConvertible`.
pointfreeco/swift-custom-dump 0.5.0
A collection of tools for debugging, diffing, and testing your application's data structures.
⭐️ 554
πŸ•“ 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.5.0
2 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
8 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
28 weeks 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
36 weeks ago
- Fixed: Null pointers no longer cause the dump function to crash, and are instead printed as `(null pointer)`
0.2.0
39 weeks ago
- Updated: Improved dumping of errors bridged to `NSError` (thanks @aroben). - Updated: Inline types no longer include `(unknown context)` in their dumps. - Fixed: Swift 5.5 support on macCatalyst, Linux, and Windows (thanks @klundberg, @davdroman). - Infrastructure: CI improvements, including running on Windows and against more versions of Swift (thanks @Jeehut, @davdroman).
0.1.3
40 weeks ago
- Added: a bunch of new conformances (thanks @noppefoxwolf, @konomae, @Bellaposa). - Fixed: macOS builds on Big Sur using Xcode 13 RC no longer fail.
0.1.2
43 weeks ago
- Added: more conformances for Photos, StoreKit, and UIKit (thanks @larryonoff). - Fixed: a build failure for watchOS in Xcode 13. - Infrastructure: continuous integration now run tests and builds for release on all Apple platforms over a number of recent Xcode versions.
0.1.1
43 weeks ago
- Added: platform requirements. In order to get things building/archiving reliably we have added platform requirements targeting iOS 13, macOS 10.15, tvOS 13, and watchOS 6. We are open to loosening these requirements in the future but want Custom Dump to reliably build across supported versions of Xcode.
0.1.0
43 weeks ago
- Initial release!
iOS macOS watchOS tvOS
pointfreeco/combine-schedulers 0.5.3
⏰ A few schedulers that make working with Combine more testable and more versatile.
⭐️ 461
πŸ•“ 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.5.3
39 weeks ago
* Updated xctest-dynamic-overlay to 0.2.1 (#42) (thanks @mRs- !)
0.5.2
43 weeks ago
- Fixed: restore platform requirements to platforms with Combine. Due to a possible but in Xcode 13, Combine Schedulers would fail to build in release mode otherwise. - Infrastructure: fixed a README/documentation typo (thanks @kalupas226).
0.5.1
47 weeks ago
- Changed: relaxed platform dependencies to be platform independent (thanks @maximkrouk). - Infrastructure: updated documentation.
0.5.0
1 year ago
- Added: `main` static helpers on `AnyScheduler` for dispatch queues, operation queues, and run loops, so that you can shorten, for example, `DispatchQueue.main.eraseToAnyScheduler()` to `.main` in many cases. - Changed: static `immediateScheduler` helpers have been shortened to `immediate`, and new, static `immediate` helpers have been defined directly on `AnyScheduler` so that you can simply pass `.immediate` to endpoints expecting an `AnyScheduler`. - Changed: static `testScheduler` helpers have been shortened to `test`.
0.4.1
1 year ago
Fixed: watchOS compilation.
0.4.0
1 year ago
- Added: an animated scheduler for UIKit. - Added: FailingScheduler, a scheduler that causes XCTest cases to fail.
0.3.1
1 year ago
- Fixed: 0.3.0 introduced a breaking change where compilation could fail in certain environments.
0.3.0
1 year ago
- Added: `Scheduler.animation()` and `Scheduler.transaction()` helper methods for SwiftUI.
0.2.0
1 year ago
Added: public initializer for `AnyScheduler`. Infrastructure: improved documentation, autoformat code.
0.1.2
1 year ago
- Fixed: timer publisher tolerance is now zero, matching what Apple does in the Swift repo.
iOS macOS watchOS tvOS
pointfreeco/swift-prelude 0.1.2
🎢 A collection of types and functions that enhance the Swift language.
⭐️ 407
πŸ•“ 7 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
pointfreeco/swift-validated 0.2.1
πŸ›‚ A result type that accumulates multiple errors.
⭐️ 367
πŸ•“ 35 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.
The NonEmpty Bugfix Edition
2 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
3 years ago
This (very) minor update ensures that CocoaPods users can merely `import Validated`.
Swift 4.2 Linux Support
3 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
3 years ago
The first release of Validated: a result type that accumulates multiple errors.
pointfreeco/swift-gen 0.4.0
🎱 Composable, transformable, controllable randomness.
⭐️ 244
πŸ•“ 7 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
7 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
1 year 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-identified-collections 0.4.0
A library of data structures for working with collections of identifiable elements in an ergonomic, performant way.
⭐️ 227
πŸ•“ 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.4.0
5 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
35 weeks ago
- Improved: performance of `IdentifiedArray.==` (thanks @mihaho).
0.3.1
37 weeks ago
- Fixed: Identified arrays that specify a key path should no longer fail equatable checks when elements are equal (thanks @sroche27r).
0.3.0
40 weeks 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
43 weeks 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
49 weeks ago
- Fixed: `removeLast(n:)` renamed to `removeLast(_:)` (thanks @konomae). - Fixed: dependence on Swift Collections relaxed to 0.0.1.
0.1.0
49 weeks 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-enum-properties 0.1.0
🀝 Struct and enum data access in harmony.
⭐️ 197
πŸ•“ 44 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.
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-url-routing 0.2.0
A bidirectional router with more type safety and less fuss.
⭐️ 183
πŸ•“ 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.2.0
5 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
7 weeks ago
Our first release!
pointfreeco/swift-html-vapor 0.4.0
πŸ’§ Vapor plugin for type-safe, transformable HTML views.
⭐️ 64
πŸ•“ 44 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
44 weeks 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
3 years ago
macOS linux macOS iOS
pointfreeco/xctest-dynamic-overlay 0.2.1
Define XCTest assertion helpers directly in your application and library code.
⭐️ 61
πŸ•“ 43 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.1
43 weeks ago
- Changed: `XCTFail` functions are now no-ops in non-DEBUG builds to avoid leaking symbols into RELEASE builds.
0.2.0
46 weeks ago
- Changed: `XCTFail` is no longer restricted to DEBUG builds.
0.1.1
49 weeks ago
- Includes MIT LICENSE.
0.1.0
1 year ago
* Initial release!
pointfreeco/vapor-routing 0.1.1
A bidirectional Vapor router with more type safety and less fuss.
⭐️ 55
πŸ•“ 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.1.1
4 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
7 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.
⭐️ 53
πŸ•“ 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
> 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
1 year 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/composable-core-motion 0.1.1
A library that bridges the Composable Architecture and Core Motion.
⭐️ 15
πŸ•“ 43 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.1
43 weeks ago
- Fixed: removed broken protocol conformance (thanks @andreyz). - Fixed: corrected README typo (thanks @barksten).
0.1.0
1 year 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.
⭐️ 12
πŸ•“ 44 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.
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!
3 years ago
linux macOS iOS

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