Twitter | Search | |
Recoil
Recoil is an experimental state management system for React.
29
Tweets
1
Following
2,392
Followers
Tweets
Recoil Jun 5
Replying to @HamedMamdoohii
Yes, someone at FB is working on a comprehensive dev tools and in the meantime I've also seen a couple of people post basic loggers. (Unfortunately I can't find them at the moment)
Reply Retweet Like
Recoil retweeted
Husek Jun 4
Replying to @sseraphini @recoiljs
After a few rounds of testing, I've started migrating one of my codebases to since it seems to be the right tool for this task in particular. It's no excel, but a Photoshop-like editor, with lots of 'isolated nodes' as well. I'd say Recoil definitely proved its value.
Reply Retweet Like
Recoil retweeted
Alejandro Beltrán Jun 4
The gist of : • Set <RecoilRoot> • Define atoms to represent your state • Consume (read & write) atoms/state from your components • Compute derived state with selectors Familiar, and straightforward. I like it.
Reply Retweet Like
Recoil retweeted
Jared Palmer May 29
Working on a little 🌀 selector/atom debugger.
Reply Retweet Like
Recoil Jun 2
Replying to @mysticaltech
If you're new to React I would suggest just using React by itself. That is enough for most apps. If you run into anything you can't solve using just React then think about introducing ancillary libraries.
Reply Retweet Like
Recoil retweeted
sveta.slepner Jun 2
My new article on RecoilJS, the new React State Management Library! In the article - why is it awesome even if it's not official yet, some background to what led Facebook to develop it, and some nice demos to help you get started!
Reply Retweet Like
Recoil Jun 2
Recoil 0.0.8 released with bug fixes and some new functionality.
Reply Retweet Like
Recoil May 26
Replying to @adnux @sseraphini
Recoil async selectors are for querying time-invariant data, so they're conceptually pure functions of their inputs, just functions that might be evaluated on some other process or host. For changing data, explicitly model time. For read-write of entities use Relay.
Reply Retweet Like
Recoil May 26
Replying to @sseraphini
It also solves the 'synchronously' part as updates are scheduled through React.
Reply Retweet Like
Recoil retweeted
Sibelius Seraphini May 23
You can do data fetching using selectors check by yourself here
Reply Retweet Like
Recoil retweeted
Parker Henderson May 23
Playing around a bit with today and this is the firat state management library for React that hasn’t confused the hell out of me. Let’s see how it goes on a more complicated project.
Reply Retweet Like
Recoil May 20
Replying to @ThePaulMcBride
Nope. Not yet.
Reply Retweet Like
Recoil May 20
Replying to @Sawtaytoes
The things we expect to change significantly are marked as UNSTABLE or DEPRECATED. The rest we do not expect to change, although we can't 100% promise that. We have a lot of code on our end we'd need to migrate for any changes, too.
Reply Retweet Like
Recoil May 19
Replying to @Sawtaytoes
It's just an opaque object. All that's done with it in order of importance is: 1) type parameter can be type checked 2) map key 3) instanceof to distinguish from non-atom things (which enabled some convenience features).
Reply Retweet Like
Recoil May 19
Replying to @danituits @sseraphini
For effects use useEffect in a subscribed component.
Reply Retweet Like
Recoil May 19
The keys are used for persistence, so they have to be stable across time. That's why they can't be symbols. In practice this doesn't seem to cause problems for us. If you want you can have a lint rule that enforces module name prefixes.
Reply Retweet Like
Recoil retweeted
Reason Bangalore May 17
bindings for the new with safeguards at compile time
Reply Retweet Like
Recoil May 19
Replying to @Sawtaytoes
The keys are used for persistence, so they can't be symbols (have to be stable across time). Persistence plus code-splitting without code-gen is the design constraint. I don't have a good solution for uniqueness other than a linter that enforces module prefixing or the like.
Reply Retweet Like
Recoil May 15
Great thread from MobX author comparing MobX and Recoil.
Reply Retweet Like
Recoil May 15
Replying to @ReactEurope @mcc_abe
Just to clarify, Concurrent mode compatibility is "coming soon". This is an early preview, and there is still some more work we'll need to do, but we're collaborating with the React team on the solutions. The API is designed for CM though so we expect no API changes for CM.
Reply Retweet Like