If anyone's interested, I maintain a list of Redux-related addons and utilities over at <a href="https://github.com/markerikson/redux-ecosystem-links" rel="nofollow">https://github.com/markerikson/redux-ecosystem-links</a> . Includes just about every vaguely-useful-looking middleware, action-generation utility, devtool, store enhancer, fill-in-category-here, that I've seen out there.<p>(And yes, I already had redux-query in the list before this post :) )
I love react, with the reusable components and the ergonomic of jsx but I really don't like what redux does to your code: it involves too much magic, you lose the concept of independent components and every change becomes a global one: everybody is notified of the inner state of each component …<p>To me it just break all encapsulation and just lead to massive tangled code that is really hard to maintain …<p>Edit: I want to clarify what I mean with the «too much magic» part. It's not redux itself which has too much magic in it, just your application flow that becomes magic when using redux, especially with libraries like the one showed by this article or redux-form[1].<p>[1]: <a href="http://redux-form.com/" rel="nofollow">http://redux-form.com/</a>
This is really cool! We have been using react-refetch from Heroku [1] for a similar purpose and it will be nice to have all our state in Redux. Another perk is that LogRocket [2] will capture this data now :)<p>[1] <a href="https://github.com/heroku/react-refetch" rel="nofollow">https://github.com/heroku/react-refetch</a>
[2] <a href="https://logrocket.com/" rel="nofollow">https://logrocket.com/</a>
Heh, I made the same thing but with global endpoints and swappable drivers so that components can be shared and endpoints can be stubbed/mocked: <a href="https://gitHub.com/tonyhb/tectonic" rel="nofollow">https://gitHub.com/tonyhb/tectonic</a><p>Think that genraally we're learning that these things should be automated for us: loading data traditionally sucks. GraphQL is really where it's at!<p>edit: that mobile keyboard though...
I've been having this discussion both in my own head and with my team for the last couple of weeks and have been thinking about how to implement something like this (but haven't got around to it). Looks great!
I've been experimenting with using a component to fetch data.
The data to fetch is declaratively described as props.<p><a href="https://github.com/limscoder/react-wrangler" rel="nofollow">https://github.com/limscoder/react-wrangler</a><p>It uses immutable and allows for time travel debugging.
This is cool, I was looking a library which would help me with CRUD and paging data recently and there weren't a lot of great options. So I started working on a library which ended up looking kind of similar to this.<p>One of the goals I've had is to stay encapsulated and not force any decision on the developer for the request library like redux-query does. I also try to avoid touching their data.<p>It isn't quite flushed out all the way, and needs more test, but I've started using it and enjoyed the way it works.<p>I'd love any feedback if anyone wanted to check it out,
<a href="https://github.com/SpinGo/crudux" rel="nofollow">https://github.com/SpinGo/crudux</a>
This looks like a really great library for simplifying API interactions.<p>I'm curious though if there's any way to indicate that a component depends on more than one end point. Would you just wrap it in multiple `connectRequest` wrappers?
I'm very surprised that Relay is not getting more traction in this space. Given, it's a lot of work to get it set up and running but once it's in place it's great. I haven't found a library that manages network state and the associated difficulties that come with it better.<p>No reason why you cannot combine both Redux + Relay, in fact once the app gets to a certain size and you want to rely less on passing around long chains of callbacks and state objects then you pretty much have to implement either Redux, Mobx or similar.
Everyone says redux and react make for great component isolation.<p>How many of you people who use this combo can swap redux out at a whim, for another state management tool? How many of your components have been modified to work with the opinions of redux? Why do i need to couple my components with redux using connect()?<p>In my experience, redux and react on there own present decent patterns to simplify UI experience, but ive never seen a discussion that involves them that doesnt couple one with the other.
Nice component, we are working internally on something same, but for Kotlin.Js + React (nothing to show yet), but i have one question:<p>How to solve a problem when same entities have different fields, for example: List of members of a chat should display avatar, name and username, but viewing profile usually use much much more data to display. How to merge them? How to keep fields in sync and not to download everything in all requests. For example, loading all members can be slow when fetching full user profiles and should be avoided.
I don't understand how this solution differs from actual side-effects managing libraries such as redux-saga or redux-cycles. Network requests are certainly side-effects and putting all their logic together with your Container code seems like a code-smell.