Answer the question
In order to leave comments, you need to log in
Are there ways to speed up redux development?
I read the basic documentation, sat down to make an application and freaked out at how slowly everything is moving forward.
To write the simplest todulist on asynchronous requests, you need to spend at least a couple of hours, although on a bare react it’s quite possible in 30 minutes.
While you write actions in a separate file, reducers, you will create a separate container, stateless - the component takes a lot of time. Also, running through different folders and files to check everything is also very inconvenient.
Is this inevitable or am I doing something wrong?
Answer the question
In order to leave comments, you need to log in
there is no need to hurry because there is no need for redux, this is a simple project so that you understand the flow. And where it is really needed, working with it does not slow down development, but systematizes the project structure and adding new features becomes very simple and obvious.
So after that, learn to determine which redux project will go into, and which one can do without it. Especially given the popularization of graphql, the development of the context API, the imminent release of hooks and other goodies.
Now there are a lot of libraries that automate the creation of selectors / reducers / actions, you can google it.
But all this raises the level of abstraction, so in my own experience it’s faster for me to do without all this, I use such a zoo: redux, reselect, redux-thunk, axios, the rest is handled.
If you do not like redux in this regard, then I can advise you to switch to mobx. But I do not like it, in terms of support and finding bugs. But of course it all depends on the project. On a small one, it may well be reasonable to use mobx.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question