-
Listener Middleware
Streamlined a Redux application by consolidating logic into slice files, removing unused code, and setting up path aliases. Transitioned from Sagas to Listeners for simpler scenarios, focused on local storage interactions and reacting to dispatched actions. Additionally, removed unnecessary dependencies like redux-saga and reselect and created a custom Persistence class for typed local storage access… Read More
-
RTK Query
I transitioned my Redux application to use RTK Query for API calls. This reduced the need for selectors and simplified data management. While RTK Query is powerful, it has limitations like needing many endpoints for a single server and requiring complex TypeScript types for builders. Sagas are still used for specific cases like handling drag-and-drop… Read More
-
Slicing Drag & Drop
Separating Drag & Drop data into its own slice. Read More
-
Transitioning to createSlice
The blog post details transitioning to Redux Toolkit’s createSlice for managing async actions, including fetch operations, drag-and-drop, and abortable processes. It highlights a modular approach using custom action groups to streamline lifecycle management, reduce boilerplate, and maintain flexibility with Redux Saga for handling complex asynchronous workflows. Read More
-
Dragon Drops
Exploring the challenges of implementing drag-and-drop in React using Material UI and React DnD. A custom library to address these challenges was created, providing reusable components and hooks for managing draggable and droppable elements. The library offers flexibility and control over drag-and-drop behavior. Read More
-
Redux Saga Routines
This blog post explores the challenges of using the Redux Saga Routines library with TypeScript and presents a custom action builder solution as an alternative. The action builder provides a more flexible and type-safe way to create Redux actions, addressing the limitations of the Redux Saga Routines library. The post also discusses the process of… Read More
-
React to Angular
The document describes the transition from React to Angular and the challenges faced. Initially, there was success with React, but Angular was found to be slower, more complex, and requiring a more rigid structure. Specific frustrations include Angular’s reliance on TypeScript, the need for decorators, complicated state management, and excessive imports. React’s simpler lifecycle management,… Read More