Narek Mailian

Hi! I've checked this and it indeed seems like a bug. I'll investigate further...!

Sounds like something that might be a good addition. I'm thinking of adding the possibility of custom push/modals as well (for instance, if you want to push to an alert,...

Hi! Sounds like a good idea, I'm sure it will be useful for others as well. I'll look into it!

Hi! Your assumption is correct. Hmm, a bit of a tricky layout, but should be doable. I haven't tried this solution, but by adding a third coordinator I think it...

This might actually be a bug. When I designed this, I didn't think anyone would ever push something to a coordinator which isn't the one at top of the stack,...

Hi! Instead of a TabCoordinatable, a NavigationCoordinatable can also be used with your previous workaround @Goktug. Then you don't need to hide the tabbar globally - and instead of switching...

Hi! Here is a quick and dirty example: ```swift class BurgerOpener: ObservableObject { @Published var value: Bool init(value: Bool) { self.value = value } } class SplitViewCoordinator: Coordinatable { typealias...

The reinitialization of the ViewModel sounds more like a SwiftUI issue than a Stinsen one (although it might be, but I checked the code quickly and it seems like we...

The second part of your problem is intended behavior. If you embed a NavigationViewCoordinator inside another NavigationViewCoordinator twice you will get duplicated navigation bars, just like if in SwiftUI you...

Yes, I agree. `RouterStore` should work the same way as `EnvironmentObject`. `RouterStore` is a bit tricky, but I'll take a look at this use case and see if it is...