Javier Chávarri

Hm, I was trying to create an isolated case and ran into a different issue 😅 When trying to add the slots the function used in `createComponent` there is an...

Thanks a lot @jaredly ! Your suggestions and the Fluid code (amazing progress btw! 😮 ), plus some hints from @cristianoc –who helped me offline– brought me back to the...

> So I guess the next steps here are: > - Decide if we should put this reconciler here in reason-reactify, or split out a revery-core project? > - Decide...

Ah, sorry for misunderstanding! 🙂 I insisted on that point because I've thought many times in the past that one of the missed opportunities from React was precisely this: because...

Cross posting from https://gist.github.com/lpalmes/8f771d2a700bd2a1172d73286ec75b19#gistcomment-2798693: Some thoughts: ### Supporting two models (class-based and hooks-based model) or just one I think that creating a shared interface between reconcilers will be very challenging...

I have been talking a bit with @cristianoc about hooks and how their rules could be encoded in the type system, and he shared with me some time ago an...

I played a bit with the "`hooks` carrying" solution, and one small downside is that it doesn't prevent users from not passing the `hooks` value around, in which case the...

@bryphe Glad you're on board with the idea! 😄 > We'd essentially just add one rule to our Rules of Hooks - use let.Hook for hooks. I think with a...

@bryphe Another downside: there is an extra function call that has to be made to call the callback passed to the hook to get the results back. I mention this...

I started something in https://github.com/jchavarri/reason-reactify/commit/02b8643d0a10d1367a57a60410a336e9a7db889c. I'm struggling with some typing issues, because the callback in `useState` returns a type `hook(state('a))`. This goes against all the current type assumptions, where all...