typesafe-actions

education. It introduce the concept of immutability, higher order function. I learn a lot from it. Nevertheless, it is a pain to use on big projects. React's setState is friendlier to devs. Unstated https://github.com/jamiebuilds/unstated (but not unstated-next), is a detached version of React's setState with additional `.subscribe` method and Promise as return. It is very good in both developing and communicating business flow. UnstatedContainer method can be treated as counterpart of Redux's action. What is missing now from the client-side web development is an in-app event library. Usually people would put domain-objects to Redux to solve the inter-component communication. This is, against the functional programming (which promotes immutability, higher order functions), introducing the possibility side-effect. In-app event library should replace this behavior so that messages can be passed through events from one component to another that resides on different component-tree, which may want to act differently. This is some sort of implementing mini kafka/rabbit-mq-like behavior inside the your web app with minimum resource required.

tate { readonly isLoading: boolean readonly isErrorLoading: boolean readonly allIds: number[] readonly byId: { readonly [key: number]: IUser } } const defaultState = { isLoading: false, isErrorLoading: false, allIds: [], byId: {} } const reducer = (state: IState = defaultState, action: IActions) => { // narrowing on types switch (action.type) { case FETCH_USERS_BEGIN: return { ...state, isLoading: true, isErrorLoading: false } case FETCH_USERS_SUCCESS: return { ...state, byId: action.payload.reduce( (acc, u) => ({ ...acc, [u.id]: u }), {} ), allIds: action.payload.map(u => u.id), isLoading: false, isErrorLoading: false } case FETCH_USERS_ERROR: return { ...state, isLoading: false, isErrorLoading: true } default: return state } } [1]: https://github.com/piotrwitek/typesafe-actions#1-classic-js-...