Explore >> Select a destination
|
You are here 
|
sandroroth.com | ||
| | | | |
github.com
|
|
| | | | | A JS library for predictable global state management - reduxjs/redux | |
| | | | |
antongunnarsson.com
|
|
| | | | | A collection of things to avoid in React components | |
| | | | |
mbuffett.com
|
|
| | | | | Recently I migrated my side-project from Redux, which I've used in every React project for the past four years, to pullstate, here is my tale. Problems with Redux Feel free to skip this part if you already know the pain points of Redux, there's nothing in here that hasn't been discussed a million times before. These are the problems as I see them, most important first: The boilerplate. Oh man, the boilerplate. Want to add a counter? First, add the field to your interface (I'm assuming TypeScript), add a default value, create a new action type for the incrementing, write an action creator, add the case to your reducer, add the dispatcher hook to your component, dispatch your action creator. It's exhausting just to list the steps, nevermind actually doing it f... | |
| | | | |
www.binovarghese.com
|
|
| | | Traditionally, you pass information from a parent component to child component via props in React. But data passing through this props drilling can make your code verbose and inconvenient if you have more components in the middle, or if many components in your app need the same information. | ||
