You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We can use thunks and stuff to lazily evaluate the UI. But the action$ is going to have a new reference every time so lazily evaluating with the listOf component is helpless. However, what if there was some way of computing stream.eq(prevAction$, nextAction$)? We could feasibly do this by keeping track of the forwarding going on.
Maybe I'm barking up the wrong tree, but its frustrating that this list componnt is going to cause all items to rerender regardless.
The text was updated successfully, but these errors were encountered:
If I'm understanding this correctly, the issue is that your update function is just re-generate the entire list on each action, regardless of if it actually changed anything. Is that correct?
Yes. Well mostly. The thing is the function reference changed, but its still the same stream and the same forwarding. So its effectively equal even though it isnt referentially equal. Here's an example of what I'm thinking.
The issue I'm trying to solve is tying to make this listOf function more performant:
https://github.com/paldepind/functional-frontend-architecture/blob/master/examples/nesting/js/list.js#L38
We can use thunks and stuff to lazily evaluate the UI. But the action$ is going to have a new reference every time so lazily evaluating with the listOf component is helpless. However, what if there was some way of computing
stream.eq(prevAction$, nextAction$)
? We could feasibly do this by keeping track of the forwarding going on.Maybe I'm barking up the wrong tree, but its frustrating that this list componnt is going to cause all items to rerender regardless.
The text was updated successfully, but these errors were encountered: