Skip to content

Conversation

JaggerJo
Copy link
Member

Current situation: If the render function of a component closes over/captures

state that state is stale. This is the case because we never change the render function - even tho it's instantiated.

This change makes it possible to access outer state and re-render when captured state changes.

This is still a prototype.

…captures

state that state is stale. This is the case because we never change the render
function - even tho it's instantiated.

This change makes it possible to access outer state and re-render when captured
state changes.

This is still a prototype.
… requires not using an FSharp

function as getting the address of a function type is prevented by the compiler. I guess casting the
function to an object might have also worked here.

- simplify bindings by passing in the RenderFunctionProperty
@JaggerJo JaggerJo changed the title Patch Component render function [DRAFT] Patch Component render function Apr 14, 2024
@JaggerJo JaggerJo marked this pull request as draft April 14, 2024 12:47
@JaggerJo JaggerJo self-assigned this Apr 14, 2024
… functions. This works but is

still a bit messy.
Component: plain old component, unchanged from master

ClosureComponent: component that works well with render function that captures state
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant