3 ms·
> view = func(state). If this was actually how it worked, I'd have much less problem with react. What I mean, specifically, is that not all function dependenc
by recursive 3y ago
> view = func(state).
If this was actually how it worked, I'd have much less problem with react. What I mean, specifically, is that not all function dependencies are explicit. This makes it look like the state is passed into some function. And then the view is returned, depending only on state. In reality, half the state is passed in (as in the argument to a function call), and half comes out of some mysterious hook storage structure. If the state was really a function argument, you could easily inspect the whole state in a debugger. Instead of... I'm not sure how you'd actually do that.
- laurencerowe 3y agoReact Developer Tools makes it easy to inspect component state in your browser. https://react.dev/learn/react-developer-tools https://react.dev/learn/react-developer-tools
- jbritton 3y agoThis brings up other questions too. Is the state on the client? How does one reconcile the server state and the client state. Is the client state a subset of server state? Is the client state a tree matching the view tree? Does the state contain only the UI data to be rendered or is it all app state.