Ummm... I'd question your terminology here. The view is dependent on the state, so the view body will be *evaluated* in order to see if there are any changes that need to be *rendered*. If there are no apparent changes, then it's not rendered (e.g. changes redrawn to the screen). Evaluating the view tree and rendering the resulting changes are two different operations. That said, and as mentioned, the technique has a lot of merit in large applications as it can greatly minimize the number of views in the tree that need to be evaluated on any given state change. Pedantic, yes, but "rendered" has a rather specific meaning.
Well explained 👍🏻
Extremely useful video. Thanks a lot! I had exactly this problem and couldn’t fix it in an app that I’m working on.
Nice concise example, thanks!
very informative video, thank you
Ummm... I'd question your terminology here. The view is dependent on the state, so the view body will be *evaluated* in order to see if there are any changes that need to be *rendered*. If there are no apparent changes, then it's not rendered (e.g. changes redrawn to the screen).
Evaluating the view tree and rendering the resulting changes are two different operations. That said, and as mentioned, the technique has a lot of merit in large applications as it can greatly minimize the number of views in the tree that need to be evaluated on any given state change.
Pedantic, yes, but "rendered" has a rather specific meaning.