I have an ambient value, that updates everywhere e...

# compose

[andrew]

I have an ambient value, that updates everywhere else in the UI, but inside here.

[andrew]

Heres a demo of that

device-2019-10-28-165255.mp4

[andrew]

So it seems ambient doesn’t have an @Model annotation, like state does

[andrew]

how can I shim that in?

[andrew]

Why would I do it like that? I need the RouterSwitch component to recompose

[Ryan Mentley]

You need the Stack to recompose - the RouterSwitch isn't actually using the history value

[Ryan Mentley]

but hmm, I'm not 100% sure what our current strategy for comparing lambdas is - I'd expect it to either recompose the Stack on ambient changes because it recomposed the parent and it passed a new lambda, or to fail to detect changes to the block, with my guess being the former

[Ryan Mentley]

but either way, you definitely shouldn't need to read the ambient outside of the Stack

[andrew]

If it helps, my History class has a model, and I don’t think the ambient will recompose anythingg

[themishkun]

@andrew why would you need the history as an ambient? You can just pass it to the top level composable which can decide based on this data which screen should be visible

[andrew]

There can be nested routes or components that want to be history aware