Using delegate vs NavigationLink

[captadoh]

I am curious if anyone can explain why in the SyncUps example is this done (using the delegate pattern back to the AppFeature)

https://github.com/pointfreeco/swift-composable-architecture/blob/main/Examples/SyncUps/SyncUps/SyncUpDetail.swift#L94

versus doing the NavigationLink like here https://github.com/pointfreeco/swift-composable-architecture/blob/main/Examples/SyncUps/SyncUps/SyncUpDetail.swift#L149

[stephencelis]

@captadoh The delegate pattern is because we require programmatic navigation to the record screen. Navigation links are always eager and drill you down to the destination no matter what. For the record screen, though, we want to delay drilling down till the user has granted permission to record audio and transcribe the meeting.

In the case of the navigation link, it's a link to a meeting history that we can eagerly drill to, so no need to add additional logic via delegation.

[captadoh]

thank you!