redux-toolkit

#use-redux-toolk... [2] https://github.com/reduxjs/redux-toolkit/releases/tag/v1.0.4

SK with TypeScript, thunks for async data fetching, and our new React-Redux hooks API. You might also want to read through the issue comment that lays out my "Vision for Redux Starter Kit" and the problems it's meant to solve [2] I just published RSK v0.8 this evening [3] which has a couple small breaking changes (primarily renaming a `slice` field to `name` and making it required). After that, I'm hoping to nail down a couple last bits of configuration, and then push it to 1.0 within the next week or two. After that, we're going to start working on a major revamp of the Redux core docs. You can see my planned outline here [4]. The goals for the docs revamp include: - Updating the tutorials, including removing outdated concepts like references to "Flux", distracting mentions of terms or warnings that beginners don't need to worry about, adding diagrams, and finding ways to improve the explanations (like changing the "Middleware" page to explain how to _use_ middleware, rather than why they work this way). We will also add a tutorial section that shows how to use Redux Starter Kit, and recommend that people use it as the "default way to use Redux". - Adding a "Real World Usage" docs section. This would include topics like choosing async middleware, debugging, folder structures, performance, and so on. - Adding a "Style Guide" page. The Redux docs are deliberately unopinionated about things like folder structures, async middleware, structuring actions and reducers, and so on. However, we'd like to provide some official guidance on our current recommended best practices. The Vue docs have a great page with their recommendations, why they recommend certain patterns, and how strongly they recommend them, and we'd like to do the same thing here. For example, we'd recommend using a "feature folder" or "ducks" pattern for structuring files, treating actions as "events" instead of "setters", and trying to put as much logic as possible in reducers. - Adding a "Thinking in Redux" section. This would include concepts like mentally modeling actions, the history of Redux and its inspirations, how it's meant to be used, and why it works the way it does. I'd love to have additional help from the community in working on this docs revamp - I certainly can't do it all myself :) Finally, I'd encourage folks to watch my Reactathon 2019 talk on "The State of Redux" [5], where I talked about Redux's market share and how it compares to other tools, as well as future directions for the library. In addition, my post "Redux - Not Dead Yet!" [6] addresses some common questions about how things like hooks and GraphQL relate to Redux. If anyone's got questions, feel free to ask! [0] https://redux-starter-kit.js.org [1] https://redux-starter-kit.js.org/tutorials/advanced-tutorial [2] https://github.com/reduxjs/redux-starter-kit/issues/82#issue... [3] https://github.com/reduxjs/redux-starter-kit/releases/tag/v0... [4] https://github.com/reduxjs/redux/issues/3313#issuecomment-45... [5] https://blog.isquaredsoftware.com/2019/03/presentation-state... [6] https://blog.isquaredsoftware.com/2018/03/redux-not-dead-yet...

uaredsoftware.com/2019/03/presentation-state... [1] https://blog.isquaredsoftware.com/2018/03/redux-not-dead-yet... [2] https://redux-starter-kit.js.org/ [3] https://github.com/reduxjs/redux-starter-kit/issues/82 [4] https://github.com/reduxjs/redux/issues/3313#issuecomment-45...

static types).