This is an interesting topic ๐ I think as times goes by we see an evolution in the tools available for the Context API. The point about debugging features for redux is a big one, and packages like redux-persist are also convenient. However, with a little elbow grease, we can attain these benefits for use with the Context API I'm lead to believe. For example, we can write our own custom localStorage based persistence for Context. And there are tools out there to help with debugging if the React DevTools are not enough. react-waterfall seems to be an option for using redux-devtools with the Context API ๐
The tools we use are improving and making it easier for the developers in creating their app. There are developers that is already refactoring from class component to function component, maybe because of the hooks?
Given that hooks are still young, they have a lot room for improvement and may take inspiration from older tools.
This is an interesting topic ๐ I think as times goes by we see an evolution in the tools available for the
ContextAPI. The point about debugging features forreduxis a big one, and packages likeredux-persistare also convenient. However, with a little elbow grease, we can attain these benefits for use with theContextAPI I'm lead to believe. For example, we can write our own customlocalStoragebased persistence forContext. And there are tools out there to help with debugging if theReact DevToolsare not enough. react-waterfall seems to be an option for usingredux-devtoolswith theContextAPI ๐Thank you for having interest in the topic.
The tools we use are improving and making it easier for the developers in creating their app. There are developers that is already refactoring from class component to function component, maybe because of the hooks?
Given that hooks are still young, they have a lot room for improvement and may take inspiration from older tools.
It's definitely an interesting space ๐