Swiftpack.co - Swift Packages by johnpatrickmorgan

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. - Allows `NavigationStack` to be used under the hood (if available) instead of `NavigationView` by adding a modifier, e,g. `.nbUseNavigationStack(.whenAvailable)`. - Removes the need to manually call `withDelaysIfUnsupported` - instead the library will automatically do so whenever needed. - Adds UI tests for example app. - Adds support for class inheritance in navigation destinations (Thanks @ggrell!) #31 - Fixes issue #30, where the removal of a `NavigationLink` would inadvertently trigger the truncation callback. - Adds support for local destinations with: `nbNavigationDestination(isPresented: Binding<Bool>, @ViewBuilder destination: () -> V)` (#17) - Adds `NBNavigationStack.CodableRepresentation` support. Thanks @pointfreeco! - Uses a fully qualified type identifier as key, to differentiate types such as A.Foo from B.Foo (#3). Thanks @zeusent!

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. - Fix dismiss completion for iOS 14.4 and below (Thanks @BohdanDatskiv!) No longer asserts when calling `goBackToRoot()` when already at the root. (Thanks @Kondamon!) - Ensures `Binding.withDelaysIfUnsupported` runs on the main thread. (Thanks @ConfusedVorlon) - Checks count in `goBack`. (Thanks @DavidKmn) - Ensures `RouteSteps. withDelaysIfUnsupported` schedules all steps on main actor. (Thanks @DavidKmn) - Presentation and navigation can now be combined into a single routes array, removing the need for separate `PStack` and `NStack`. The new `Router` can handle both. - Convenience methods are now extensions on Array, with no more need for `NFlow` or `PFlow`, simplifying state management. - Large-scale navigation updates can now be made within a `withDelaysIfUnsupported` call, and will be broken down into smaller updates that SwiftUI supports. This works around a limitation in SwiftUI that only allows one screen to be pushed, presented or dismissed at a time. - The view builder closure for creating screens can now provide a binding to the screen so that screens can mutate their state within the routes array. - A new showing function makes it easy to have a fixed root screen which shows zero or more routes.

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. - Fixes most deprecations (thanks @jshier) - Updates library code and examples to use TCA's new ReducerProtocol. - Simplifies the API a little. - Ensures latest version of a screen is cached for display during a dismiss animation (#27). Thanks @salqueng! - Avoids unnecessary re-renders in TCARouter (#20) (Thanks to @dannyhertz) - Adds MIT licence (#15) - Presentation and navigation can now be managed in a single routes array, removing the need for separate `PresentationStore` and `NavigationStore`. The new `TCARouter` can handle both in one. - Convenience methods are now extensions on `RoutableCollection`, so this library no longer needs to duplicate the convenience methods from `FlowStacks`. - Large-scale navigation updates can now be made within an `Effect.withDelaysIfUnsupported` call, and will be broken down into smaller updates that SwiftUI supports. This works around a limitation in SwiftUI that only allows one screen to be pushed, presented or dismissed at a time. - Cancellation of in-flight effects is now managed as part of `withRouteReducer` function, which ensures effects are tagged for cancellation before combining with the reducer that updates routes. This fixes a bug where long-lived effects initiated by the coordinator would be cancelled if they were triggered by a screen that has been dismissed.