Updates to demo app and documentation for 1.2.3

Author: hmlongco

CHANGELOG

@@ -1,5 +1,10 @@
 # Navigator Changelog
 
+### 1.2.3
+
+* Updates documentation to illustrate no longer needing `navigationDestination` registration in the majority of cases
+* Fixes a few non-Navigator issues in the demo app for Xcode 26
+
 ### 1.2.1
 
 * Adds new `navigationMap` modifier for multi-module application support

NavigatorDemo/NavigatorDemo/NavigatorDemo/Application/NavigatorDemoApp.swift

@@ -50,14 +50,14 @@ extension NavigatorDemoApp{
 
     nonisolated struct InitializationTask {
         let priority: TaskPriority
-        let operation: @Sendable () async -> Void
+        let operation: @isolated(any) @Sendable () async -> Void
     }
 
     nonisolated static let tasks: [InitializationTask] = [
-        .init(priority: .high, operation: task1),
-        .init(priority: .high, operation: task2),
-        .init(priority: .low, operation: task3),
-        .init(priority: .medium, operation: task4),
+        .init(priority: .high, operation: { await task1() }),
+        .init(priority: .high, operation: { await task2() }),
+        .init(priority: .low, operation: { await task3() }),
+        .init(priority: .medium, operation: { await task4() }),
     ]
 
 }

NavigatorDemo/NavigatorDemo/NavigatorDemo/Application/TabView/ModernTabView.swift

@@ -20,6 +20,7 @@ struct ModernTabView : View {
                 }
             }
         }
+        .tint(.primary)
         // setup tab switching
         .onNavigationReceive { (tab: RootTabs, navigator: Navigator) in
             if tab == selectedTab {

NavigatorDemo/NavigatorDemo/NavigatorDemo/Features/Home/HomeView.swift

@@ -24,7 +24,6 @@ struct HomeRootView: View {
     var body: some View {
         ManagedNavigationStack(scene: RootTabs.home.id) {
             HomeContentView(viewModel: HomeContentViewModel(resolver: viewModel.resolver, title: "Home Navigation"))
-                .tint(.white)
                 .navigationCheckpoint(KnownCheckpoints.home)
                 .onNavigationReceive { (destination: HomeDestinations, navigator) in
                     navigator.navigate(to: destination)
@@ -36,7 +35,6 @@ struct HomeRootView: View {
                         .toolbarBackground(.hidden, for: .navigationBar)
                 }
         }
-        .tint(.white)
     }
 }
 

NavigatorDemo/NavigatorDemo/NavigatorDemo/Features/Settings/UnregisteredDestinations.swift

@@ -8,7 +8,7 @@
 import NavigatorUI
 import SwiftUI
 
-public enum UnregisteredDestinations: NavigationDestination {
+nonisolated public enum UnregisteredDestinations: NavigationDestination {
 
     case page1
     case page2

README.md

@@ -6,7 +6,7 @@
 
 Advanced Navigation Support for SwiftUI.
 
-## Navigator 1.2.1
+## Navigator 1.2.3
 
 Navigator provides SwiftUI with a simple yet powerful navigation layer based on NavigationStack. 
 
@@ -83,7 +83,7 @@ struct RootView: View {
 ```
 It's that simple.
 
-ManagedNavigationStack creates a NavigationStack for you and installs the associated Navigator environment variable that "manages" the stack. It provides the NavigationPath and also supports navigation options like automatically presenting sheets and fullScreenCovers.
+ManagedNavigationStack creates a NavigationStack for you and installs the associated Navigator environment variable that "manages" that particular NavigationStack. It provides it with the NavigationPath and also supports navigation options like automatically presenting sheets and fullScreenCovers.
 
 Those with sharp eyes might have noticed something missing in the above code. We're using `NavigationLink` with a destination value, but where's the `.navigationDestination(for: HomeDestinations.self) { ... )` modifier?
 
@@ -191,7 +191,7 @@ extension HomeDestinations {
 ```
 In this case, should `navigator.navigate(to: HomeDestinations.page3)` be called, Navigator will automatically present that view in a sheet. All other views will be pushed onto the navigation stack.
 
-The current navigation methods are: .push (default), .sheet, .cover, and .send.
+The current navigation methods are: .push (default), .sheet, .managedSheet, .cover, .managedCover, and .send.
 
 Predefined methods can be overridden using Navigator's `navigate(to:method:)` function.
 

Sources/NavigatorUI/Documentation.docc/Advanced/AdvancedDestinations.md

@@ -2,11 +2,13 @@
 
 Building NavigationDestinations that access the environment and other use cases 
 
-## External NavigationDestinations
+## Overview
 
 Earlier we demonstrated how to provide ``NavigationDestination`` types with a view body that returns the correct view for that type.
 ```swift
-extension HomeDestinations: NavigationDestination {
+    ...
+    case pageN(Int)
+
     public var body: some View {
         switch self {
         case .page2:
@@ -24,7 +26,9 @@ It's a powerful technique, but what if we can't construct a specific view withou
 
 Simple. Just delegate the view building to a standard SwiftUI view!
 ```swift
-extension HomeDestinations: NavigationDestination {
+    ...
+    case pageN(Int)
+
     public var body: some View {
         HomeDestinationsView(destination: self)
     }
@@ -84,7 +88,7 @@ struct HomePageNView: View {
 ```
 *See the 'DemoDependency.swift' file in the NavigatorDemo project for a possible dependency injection mechanism.*
 
-## NavigationDestinations within Views
+### NavigationDestinations within Views
 
 This technique also allows us to construct and use fully functional views elsewhere in our view code. Consider.
 ```swift
@@ -100,7 +104,7 @@ struct RootHomeView: View {
 Remember, our enumerated values are Views! Just drop the value into a view to obtain a fully resolved `HomePageView` and view model from `HomeDestinationsView`, 
 complete and ready to go.
 
-## Custom Sheets using NavigationDestination
+### Custom Sheets using NavigationDestination
 Let's demonstrate that again using a custom presentation mechanism with detents.
 
 Only this time instead of evaluating the enumerated value directly we'll do the same using a destination variable.
@@ -127,10 +131,48 @@ struct CustomSheetView: View {
 ```
 Setting the variable passes the desired destination to the sheet closure via the `$showSettings` binding. Which again allows us to directly evaluate the value and obtain a fully resolved view ready for presentation.
 
-## Cross Module View Dependencies
-Another technique that might not be apparent and you might have missed at first glance is how this gives us the ability to pass required views across features.
+Note that the `.navigationDismissible()` modifier "registers" our custom sheet with Navigator, and allows the view to be dismissed as needed when deep links and routing occurs elsewhere in the application. (See: <doc:Dismissible>.)
+
+### Modular Views
+
+We can also use this technique to expose a module's feature views *without* exposing exposing the views themselves. Consider.
+```swift
+public enum OrderDestinations: NavigationDestination {
+    case orderSummaryCard(Order)
+    case order(Item)
+    case listPastOrders
+
+    public var body: some View {
+        OrderDestinationsView(destination: self)
+    }
+}
+```
+Again, this lets us obtain and use fully constructed views from a module *without* seeing the actual views that support them, and *without* knowing any details of how they're constructed.
+```swift
+struct CustomView: View {
+    @Environment(\.navigator) var navigator
+    @State var order: Order
+    var body: some View {
+        VStack {
+            ...
+            OrderDestinations.orderSummaryCard(order)
+            ...
+        }
+    }
+}
+```
+And now the order summary card is in our view, doing it's thing.
+
+Couple that with Navigator 1.2's ability to avoid the need for `navigationDestination` registrations, and you have an extremely powerful system at your command. 
+
+If the `orderSummaryCard` has a button that takes them to an internal `OrderSummaryDetails` page, that's fine.
+
+It just works.
+
+### Cross Module View Dependencies
+Another technique that might not be apparent is how this gives us the ability to pass required views across features.
 
-Take another look at our `HomeDestinationsView`.
+Take another look at our original `HomeDestinationsView`.
 ```swift
 private struct HomeDestinationsView: View {
     let destination: HomeDestinations