react-redux-api-tools VS redux-devtools

Software boutique with experts in Python/Django, Javascript/React, and UI/UX design.

Hi I’m Artur, from Labcodes. We’re a software boutique based in Brazil. We’re results-driven and internationally recognized for our 7+ years of partnership with US companies.

We’re experts in Python/Django, Javascript/React, and UI/UX design. Our team is comfortable working together and has a strong engineering culture, which is hard and expensive to build on an internal team.

I know that engaging with an external company, even more if we reach you out on a cold approach, is risky, so I’ll leave some links with social proof of our knowledge and experience here.

Talks we gave in major Python/Django conferences https://lab.codes/talks

Client reviews https://lab.codes/clutch-reviews

React open-source libs we maintain https://github.com/labcodes/react-redux-api-tools https://github.com/labcodes/rel-events

Design portfolio https://lab.codes/design-portifolio

email me if you’re interested in doing business or get to know more about us: [email protected]

Also, you should use redux-devtools extension to get the most out of any react-redux-based project.

Use NgRx's action stream as a logging solution. Dispatch actions instead of logging. You don't have to worry about the state management part or anything either. Add the store-devtools package along with the base store package. It'll let you configure only logging while in development mode and a few other options. Then, install the Redux Devtools extension into your browser. That will give you a view of the dispatched actions and any data you want to pass along with them. It has a filter, so you can tag your actions like you normally would as described in the docs. Like, "[Log Level] [Feature] log message". Then, filter them in the dev tools to see just what you want. You can see a screenshot of it here. You may even like some of its other features and maybe you'll pick up more of the pattern as you see fit.

Redux DevTools is a browser extension that allows developers to inspect and debug Redux stores. This tool helps developers to track state changes, actions, and other data related to the Redux store. You can download it from its official GitHub repository: https://github.com/reduxjs/redux-devtools.

Redux dev tools

You can still keep your custom hooks in separate files, maybe in a folder called state. You could migrate to a state library when things start to seem unmanageable, or when you want one of the many cool features that a state library can offer, like automatically persisting parts of state to your user's storage using middleware (Redux docs, Zustand docs), easily managing API connections and query caching with RTK Query, or having a log of every state change with the ability to revert/go back in time to debug state changes with Redux Devtools (also works with Zustand).

With the redux-devtools-extension, we can now easily see all the actions that have been dispatched, as well as the current state of our store. This extension also allows us to time travel, meaning we can go back and forth through different states to see how our application got to where it is, as shown in the image below.

We need to see your RECEIVE_BENCHES action creator as well as dispatch call to tell you more. You should inspect what is going on in your reducer, either by setting a breakpoint in your editor's debug mode, by using Redux DevTools (https://github.com/reduxjs/redux-devtools), or simply by writing dirty console.log and debugger calls.

When an action is dispatched, all of the reducers will be notified and every single one of them will check if they can handle the action. Not only that, but the Redux dev tools will be a mess trying to see what action was fired when. That’s why we should try to think of actions as events that happened and not what the action is changing. For example, we should rather have an action called userLoggedIn than setUserId.