Automatically call dismiss() when binding becomes nil

[schrismartin-eb]

Hey there! In this week's episode on pointfree, you call out a rough edge on the Navigation APIs where setting a binding to nil in the a parent screen isn't necessarily dismissing a child view, but is instead just clearing it out.

I wanted to know if you considered handling this bug within the navigation library itself. And if you decided not to, why not?

[mbrandonw]

Hi @schrismartin-eb, that might be possible! We just haven't explored it yet. It's also worth noting that there are still other Apple bugs lurking in the shadows that we haven't figured out workarounds for yet. 😕 https://github.com/pointfreeco/swiftui-navigation/issues/65

[stephencelis]

It's been awhile but I think we actually did explore this...at least I did, but I wasn't able to get it to work. Something about trying to insert a dismiss inside of a custom navigationDestination view modifier's destination and drive it from a binding just wasn't working for me. I think we discussed the predicament with @tgrapperon, but none of us could come up with a solution that worked reliably.

That said, if folks do come up with a solution that could be used in the library, we'd love to see it! It's just a nut we haven't been able to crack yet.