3 ms·
That's pretty sweet. I did notice that moving back in time (thus changing the values to what they had previously been) actually caused it to think more stuff h
by notduncansmith 12y ago
That's pretty sweet. I did notice that moving back in time (thus changing the values to what they had previously been) actually caused it to think more stuff had changed, therefore increasing the number of changes to track. Still, a relatively small bug in an incredibly cool demo.
This doesn't exactly answer my question of what people are using to store data for React to use though. For instance, if I have an inbox and I want to display a list of messages, and unread counts for each folder. It makes sense to me to store that data in one place, instead of copying it to each component's state. So where does it go? Just a global POJO, or what?
- zubairq 12y agoHi, Glad you liked the demo, it is a GPL project at https://github.com/zubairq/coils https://github.com/zubairq/coils. I may have fixed the bug with going back in time, not 100% sure though, but maybe try it again as more fixes have gone in. Regarding how people are storing data for react, this is a big topic in itself. I personally (and with Coils) keep a UI only data structure which updates the React GUI, and then synchronise the state from a Data store totally independantly, although I have seen that other projects mix this up a bit, or don't give an opinion on it, which can caue misuse. Does that answer the question?