Closed 3a4oT closed 3 years ago
Interesting, I never considered making Navigator
conform to Equatable
.
I'm not well-versed with Composable architecture in SwiftUI. Is initializing a new Navigator
something that occurs? I'm curious whether a simple instance comparison would suffice or not, instead of a deep comparison:
extension Navigator: Equatable {
public func == (lhs: Navigator, rhs: Navigator) -> Bool {
lhs === rhs
}
}
Thanks!
Is initializing a new Navigator something that occurs
Not really I just pass a reference to action when I need to navigate somewhere so I'm fine to simplify things! Thanks!
Thanks! can I count on the new release any time soon?=)
BTW. for some reason, I don't see these changes on the main branch. Am I missing something? cc @frzi
I've reorganized pieces a bit as I was going through the documentation. Rest assured your changes are present in the main branch. 😉
Currently going through some things to prepare for 1.1.0, looking what to include and what not. If there's some urgency, you can tell Xcode to use the main branch instead of tagged releases in the meantime. 😉
Yeah, seems tit was a false-positive ping! Thanks
I use SwiftUIRouter with Composable architecture to make things easier I've added Equatable conformance to Navigator so it can be used in
TCA
action or state.