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
Hi! I'm curious what the long-term plan is for this library. Are there any big problems that still need to be solved? Is there a roadmap for planned features? Of course, it seems like SSR and devtools are the big things that are missing, but it would be great to have a centralized place for status updates like a GitHub wiki or something.
By the way, I really appreciate your work on this. I suspected something like this framework would be possible for a couple years now but wasn't sure how to make it real.
The text was updated successfully, but these errors were encountered:
We do have a small list of goals in the README#high-level-overview, but nothing besides that at the moment.
Let us know if you have questions about any of them. But here are some of the open problems:
We still don't know how we would test Turbine using the declarative testing feature of Hareactive.
What exactly would the user want to test?
What would be a convenient API for this?
Similar questions needs answer for allowing the user to hook into a Component's lifecycle.
What exactly would the user want to hook into?
What would be a convenient API for this?
Hi! I'm curious what the long-term plan is for this library. Are there any big problems that still need to be solved? Is there a roadmap for planned features? Of course, it seems like SSR and devtools are the big things that are missing, but it would be great to have a centralized place for status updates like a GitHub wiki or something.
By the way, I really appreciate your work on this. I suspected something like this framework would be possible for a couple years now but wasn't sure how to make it real.
The text was updated successfully, but these errors were encountered: