navigationDestination(isPresented:destination:)

[tospery]

Description

How to resolve warning in 04-Navigation-Lists-NavigateAndLoad.swift file: struct NavigateAndLoadListView: View { @Bindable var store: StoreOf

var body: some View {
    Form {
        Section {
            AboutView(readMe: readMe)
        }
        ForEach(store.rows) { row in
            NavigationLink(
                "Load optional counter that starts from \(row.count)",
                tag: row.id,
                selection: .init(
                    get: { store.selection?.id },
                    set: { id in store.send(.setNavigation(selection: id)) }
                )
            ) {
                if let store = store.scope(state: \.selection?.value, action: \.counter) {
                    CounterView(store: store)
                } else {
                    ProgressView()
                }
            }
        }
    }
    .navigationTitle("Navigate and load")
}

} the warning is: 'init(_:tag:selection:destination:)' was deprecated in iOS 16.0: use NavigationLink(value:label:), or navigationDestination(isPresented:destination:), inside a NavigationStack or NavigationSplitView

Checklist

• [X] I have determined whether this bug is also reproducible in a vanilla SwiftUI project.
• [X] If possible, I've reproduced the issue using the main branch of this package.
• [X] This issue hasn't been addressed in an existing GitHub issue or discussion.

Expected behavior

No response

Actual behavior

No response

Reproducing project

No response

The Composable Architecture version information

No response

Destination operating system

No response

Xcode version information

No response

Swift Compiler version information

No response

[stephencelis]

That case study is using some older SwiftUI APIs which are deprecated, and are there just as examples for folks still targeting <iOS 16. There are other more modern examples, as well, but we can't show them both off in the same target and avoid the warnings.

Because this isn't a library bug, and so I'm going to convert it to a discussion, but if you have specific questions we can help with, let us know!