Hello. Maybe this question is already asked but re...

# compose

[Jasmin Fajkic]

Hello. Maybe this question is already asked but really want to see how other people manage this. I need access to navcontroller deep down in child component. I do not want to do react thing “props drill” and that every piece of app knows for navcontroller event it does not need it. Is there any better approach to pass navcontroller deep down? Local composition?

[Chrimaeon]

Literally asked today
https://kotlinlang.slack.com/archives/CJLTWPH7S/p1658704651185669

[Jasmin Fajkic]

wow wow thx 😄 … same issue bother us 😄 so props drilling is our solution passing lambda around to component which actually needs it

[dewildte]

See how I pass events up with very minimal amounts of lambdas here:
https://github.com/EricDw/MADPlayground

[Ian Lake]

You might look at changing some of your intermediate layers to be more Slot based APIs if you find yourself reusing them in multiple different screens: https://chris.banes.dev/slotting-in-with-compose-ui/

[dewildte]

@Ian Lake was this comment ☝️ directed at me?

[Ian Lake]

Nope, to Jasmin. More that intermediate layers that use slot based APIs don't need to know about passing lambdas, as they work with any content 🙂

[dewildte]

True

[Jasmin Fajkic]

thx a lot @Ian Lake. One thing on the same note what is preferred way of sending objects as navigation params or it is better to use something like https://github.com/raamcosta/compose-destinations

[Ian Lake]

As per the other thread from yesterday, don't send them at all is the best way https://kotlinlang.slack.com/archives/CJLTWPH7S/p1658736921551749?thread_ts=1658736921.551749&cid=CJLTWPH7S