-
Freactal-seed - https://github.com/bingomanatee/freactal-seed - is a superset of freactal. It replaces the static "seed" for state with an object with a host of convenience methods for cretaing and se…
-
I'm not sure if you guys are looking for `freactal` to get more traction; please ignore this if you are not :).
If you are, however, I'd strongly suggest to republish your [awesome intro](https://f…
-
Create controlled input with freactal store - whenever you type a character at any cursor position, the cursor jumps to the end of input.
This repro is taken straight from the README https://github.c…
-
The idea of deferring state management to `freactal` is solid but as far as I can tell, users will still need to use class components if they want to trigger effects in lifecycle methods, and the READ…
-
Right now when you want some states, you have to create and provide it through the context using `provideState` and then inject it into your component with `injectState`. This is great when you are de…
-
Super excited to try this out. Mad props to you guys at formidable 🎉
Would someone care to help me see how freactal fits alongside some of the points from the zen of python? I'm new to this set of…
-
Consider a rendering of nested comments.
Say you build up a state provider "withReplies" that takes an id prop and fetches replies to put in the state.
This withReplies approach works great, unt…
-
I have a feeling some types would make maintaining/refactoring freactal a lot easier. I'm looking at implementing #51 and it would be helpful if everything was well typed first.
cc @ryan-roemer
-
Building on #14, I believe it's possible to eliminate the generator from RRC.
Right now, controllers rely on generators to resolve promises and to get access to the selectors and `dispatch`. They u…
acjay updated
7 years ago
-
Like [this portfolios](https://www.behance.net/gallery/21121127/Portfolio-Redesign-) for Designers