A modern programming language that makes developers happier.

kotlinlang

Hello everyone. :wave:
I'm working on a full compose app and it's awesome (in production). Recently I've followed this great article <https://medium.com/google-developer-experts/modular-navigation-with-jetpack-compose-fda9f6b2bef7> written by <@U0122QH30PP> to clean a bit our navigation logic.
I really like the fact that ViewModel are handling the Navigation but it's a debate inside my team.

I've a question for all compose-navigation-expert
• would you recommand to let the VM take the input and handle the navigation or still passing all the click events via a lambda until it reach the NavHost (in my opinion a bit heavy)
• One more question, how you handle if the navigation needs to use some `NavOptionsBuilder` for example navigation with a BottomSheet? Right now my `navigate` method takes a parameter to know which kind of navigation it needs to handle (default or bottomType), and the actual builder is created when the events is received.