react-redux VS react-redux

I'm using react/react-redux/react-router/react-router-redux.

Reactjs As seen here I am trying to decouple my app's components as much as I can and make them not aware of any storage or action creator. The goal is to have them to manage their own state and call functions to emit a change. I have been told that you do this using props. Considering // Menu.jsximport React from 'react'import { className } from './menu.scss'import Search from 'components/search'class Menu extends React.Component { render () { return ( Home foo bar ) }} And // Search.jsximport React from 'react'import { className } from './search.scss'class Search extends React.Component { render () { let { searchTerm, onSearch } = this.props return ( {searchTerm} onSearch(e.target.value)} value={searchTerm} /> ) }}Search.propTypes = { searchTerm: React.PropTypes.string, onSearch: React.PropTypes.function}export default Search And reading here I see a smart use of Provider and connect and my implementation would look something like this: import { bindActionCreators, connect } from 'redux'import actions from 'actions'function mapStateToProps (state) { return { searchTerm: state.searchTerm }}function mapDispatchToProps (dispatch) { return bindActionCreators({ dispatchSearchAction: actions.search }, dispatch)}export default connect(mapStateToProps, mapDispatchToProps)(Search) Assuming I have a store handling searchTerm as part of the global state. Problem is, where does this code belongs to? If I put it in Search.jsx I will couple actions with the component and more important to redux. Am I supposed to have two different versions of my component, one decoupled and one connect()ed and have to use it? If yes what would my files tree look like? One file per component or a like a make-all-connected.js ? Answer link : https://codehunter.cc/a/reactjs/decoupling-react-components-and-redux-connect

It is in fact a part of react-redux which is used to connects a React component to a Redux store.

React Redux (https://react-redux.js.org/)

You add the current user state to a React Context or state management library, read from it on the top bar, and write to it after a user signs in. Done. No big deal, right?

- Throws better errors in an RSC environment

- https://github.com/reduxjs/react-redux/releases/tag/v9.0.0

## Reselect 5.0:

- Switches to a new `weakMapMemoize` memoizer as default

- Renames `defaultMemoize` to `lruMemoize`

- Allows passing memoizer options direct to `createSelector`

- Many TS improvements

- https://github.com/reduxjs/reselect/releases/tag/v5.0.1

## Redux Thunk 3.0:

- Drops the default export and switches to named exports ( `{thunk, withExtraArgument}` )

- https://github.com/reduxjs/redux-thunk/releases/tag/v3.1.0

This has been a _huge_ year-long development effort!

We're thrilled to get these improvements out. The tooling and bundle improvements will help all users, and we think the features and TS changes will improve the Redux dev experience significantly.

Thank you SO MUCH to everyone who has contributed or helped test out the work!

Please file bug reports for the inevitable issues that pop up post-release!

but now I'm going off on a conf trip and going to take a very well-earned break from Redux work for December :)

redux with react-redux

Redux

react-redux : Integration with React

When your application needs a single source of truth. You'll be better off using a more powerful library like Redux

You should think about using some client state management libraries like Redux. Redux gives you the possibility to encapsulate states and manipulate it through functions. https://react-redux.js.org/