Transcript from the "Declarative UI as a Paradigm" Lesson
[00:00:25] And we will go see a JS nested list representation of your actual DOM elements and content so you can get semi-visual coding. It's very contemporary emoji choice there, right? Via nested objects or arrays of info, as we default to in UI Hobarts, all functional components, which is what we're gonna come to.
[00:01:17] If you set up one way data binding, that is a user can only affect data via the handler, and then run the update all the way through, otherwise, it's not guaranteed to be reflective. You could have things here that maybe have come through our handler, or things here that are from the user, where in fact we want any user action just to be a submission.
[00:02:37] Let's even actually map this out with some letter. So we have tended to here, and then the data flows in the JS DOM or visual DOM, convert that to the actual DOM. That's what's happening here, where we create our access to objects, and it comes to the actual DOM.
[00:03:43] We get to define that in our handler. Do not get involved in the automatic re-propagation of that to the page based on the permanent description of that one-to-one relationship between that data and what we see.