Oh hey, that's my post.
So, uh... Redux co-maintainer and author of that post here. Happy to answer questions and point people at possible solutions :)
So, uh... Redux co-maintainer and author of that post here. Happy to answer questions and point people at possible solutions :)
I contributed some of the initial documentation [1] for testing middleware back in the day.
Wondering if there are any areas in particular you'd be looking for contributions? I use redux every day and would like to contribute back some (if it would be helpful).
Beyond that... oh, boy. I'd love help maintaining my React/Redux links list [1]. I've been really busy the last few months and have fallen behind on adding new links, and it could also use some maintenance attention to look at the existing links and figure out which ones are outdated and not really useful any more.
The "starter kit" lib I threw together [2] could use more design work and ideas to figure out what other "batteries included" type things we would want to include out of the box as an official Redux-branded library to solve some of people's common pain points.
React-Redux has some open PRs related to React 16.3 [3]. It's starting to look like we need to put together a bigger v6.0 major version release with some combined changes, and it would be good to get more eyes on the situation to figure out what's needed. There's also an open PR for adding an "object shorthand" for selectors with `mapState` that's been lying around for a while waiting for someone to add some tests so that we can say we're happy with how it works and merge it.
[0] https://github.com/reactjs/redux/issues?q=is%3Aissue+is%3Aop...
[1] https://github.com/markerikson/react-redux-links
[2] https://github.com/markerikson/redux-starter-kit
[3] https://github.com/reactjs/react-redux/pulls?q=is%3Apr+is%3A...
Like let's say you decided to use GraphQL and Context API you would still need Redux in these cases?
> Yes, the new context API is going to be great for passing down data to deeply nested components - that's exactly what it was designed for. If you're only using Redux to avoid passing down props, context could replace Redux - but then you probably didn't need Redux in the first place. Context also doesn't give you anything like the Redux DevTools, the ability to trace your state updates, middleware to add centralized application logic, and other powerful capabilities that Redux enables.
> I'd agree that data fetching via GraphQL, and especially with Apollo, will likely reduce or eliminate your data-fetching related Redux code. And again, if that's all you were using Redux for, you probably wouldn't need Redux after moving all the data-fetching handling into Apollo. ... But, as with context, I'd say there's definitely use cases where Redux is going to work better than GraphQL + Apollo, and possibly without requiring as much buy-in throughout your architecture.
Dan Abramov's "You Might Not Need Redux" post [0], which I linked a couple times in there, lists a variety of use cases where Redux absolutely shines.
[0] https://medium.com/@dan_abramov/you-might-not-need-redux-be4...
I haven't had time to try it myself, but it looks conceptually interesting.