Thomas Honeyman

Sorry, didn’t mean to mark this ready to review 😅 thanks for adding this! To be honest I wrote the core of this in a few hours and haven’t looked...

While I am open to a Hooks version of Formless, I'm not currently planning to work on this. I did implement a working Hooks version of Formless, but I never...

Thanks for the report, @hrajchert. I haven't seen this happen before. If I'm following correctly, you have: * an `instantInput` that is raising an output message to some parent *...

Thanks for pointing this out, @milesfrain. I think there are two things we can do for now, and maybe we can do even more in the future to make this...

I've added labels for this as it's something that could be added to the project documentation (even if just by copy/pasting my description into the docs somewhere).

I'm not entirely sure what you mean. Do you mind explaining a bit more what you have in mind?

I agree that the `captures` documentation could use some improvement and with the three places you've identified as places it could see changes. > Change the language here to clarify...

@marcusbuffett as @JordanMartinez noticed and we briefly talked about on Slack, the problem is that it’s not safe to pass HookM code between components (though it’s perfectly fine to pass...

> I think it would be nice if one run code defined in one component in another component. When you write some code in `HookM` it doesn't matter where you...

There are essentially two possible approaches here: 1. Use a reference to the component as part of the state identifier (hidden from the user). If the state identifier is used...