Quick Q: when updating a larger data source, will ...

# glance

[andrew]

Quick Q: when updating a larger data source, will it only update if the snapshotted state definition is not equivalent? I don't use state definitions because I'm trying to avoid doing a data duplication dance with react native

If this is the case, is there a way to force an update? I'm thinking of just storing the last updated timestamp in millis to force this, hacky, but would probably work. I'd like to avoid this Edit: tried this, and realized it wouldn't work! The current composition doesn't get recreated (duh).

[andrew]

This is also how initial data is passed in

[andrew]

I might end up making a hacky datastore wrapper around room to fulfill the state definition part

[andrew]

Though, if there's an official or backdoor way to do this (not using data) store, that'd be amazing 🙏🏻

[Summers Pittman]

I might be misunderstanding, but you can just use a normal repository pattern and reference a state flow and it will update/recompose normally

[andrew]

True, but I'm inheriting code 😐

[andrew]

I will get to renaming it

[andrew]

That, and we cant really observe flows inside the widget

[andrew]

At least as far as I know

[Summers Pittman]

You can

[andrew]

Hmmmm, if that's the case, that definitely changes things

[Summers Pittman]

https://gist.github.com/secondsun/e6f975b48185a36abf7777ddd9a1eefc

[andrew]

And will it update from a cold start?

[Summers Pittman]

So there's some caveats to it, you are still bound by the timeouts that the workers and receivers have to live by. For quick updates (like updating a message "I'm loading from disk" ->"I'm ready to work") it does will. I would think form a cold start your app would still need to kick off the updates

[andrew]

Gotcha, in my case, you interact inside the app, and the widget should update

[andrew]

I'll try this real quick

[Summers Pittman]

I think the flow only stays alive for about 10 seconds, but when you update the widget from the app the widget will start watching the flow until it gets timed out.

[andrew]

So it's working like magic 🙂

[andrew]

This is awesome 🤩

[andrew]

I would have thought any work done with a flow would be ignored once it is "dead"

[andrew]

So it seems to work half the time