jiti-meet/react
Lyubo Marinov 7f8e8177d0 [RN] Refactor "Keep track of ongoing network requests" and "Show a progress indicator in the BlankPage"
I'm not saying that the two commits in question were wrong or worse than
what I'm offering. Anyway, I think what I'm offering brings:

* Compliance with expectations i.e. the middleware doesn't compute the
next state from the current state, the reducer does;

* Clarity and/or simplicity i.e. there's no global variable (reqIndex),
there's no need for the term "index" (a.k.a "reqIndex") in the redux
store.

* By renaming net-interceptor to network-activity feels like it's
preparing the feature to implement a NetworkActivityIndicator React
Component which will take on more of the knowledge about the specifics
of what is the network activity redux state exactly, is it maintained by
interception or some other mechanism, and abstracts it in the feature
itself allowing outsiders to merely render a React Component.
2017-08-29 18:54:04 -05:00
..
features [RN] Refactor "Keep track of ongoing network requests" and "Show a progress indicator in the BlankPage" 2017-08-29 18:54:04 -05:00
.eslintrc.js Fix typo 2017-07-26 10:40:05 -05:00
index.native.js [RN] Fix root component's prop types 2017-07-31 15:30:31 +02:00
index.web.js [RN] Naming 2017-06-09 14:51:31 -05:00