Replies: 2 comments
-
I believe in their videos about Observability, they say it's okay for certain actions to be executed multiple times (like setting a button's attributes to the same value), which is why it should be okay to just utilize one observe closure in your code. The exception is for computationally-intensive code like reloading a UITableView's data, in which case you do want to have that in a separate closure. |
Beta Was this translation helpful? Give feedback.
-
Hi @nmalevich, this is discussed in the docs here:
|
Beta Was this translation helpful? Give feedback.
-
I have explored migrating guide and projects from examples, but I haven't found answer for my question about observe{} and ObservableState.
For what we can separate observe{} if all of our separated parts of observe execute when we change only one property in ObservableState
Beta Was this translation helpful? Give feedback.
All reactions