redux

问题 I searched a bit about this question but found very vague answers. In redux, we know that the state is stored as an object. But where is this state stored actually? Is it somehow saved as a file which can be accessed by us later on? What I know is that it does not store it in a cookie format or in the browser's local storage. 回答1: The state in Redux is stored in memory, in the Redux store. This means that, if you refresh the page, that state gets wiped out. You can imagine that store looking

问题 I searched a bit about this question but found very vague answers. In redux, we know that the state is stored as an object. But where is this state stored actually? Is it somehow saved as a file which can be accessed by us later on? What I know is that it does not store it in a cookie format or in the browser's local storage. 回答1: The state in Redux is stored in memory, in the Redux store. This means that, if you refresh the page, that state gets wiped out. You can imagine that store looking

问题 I have a scenario where I'm passing data from a reducer into my react state. data: { "id": 1, "title": "Test", "content": { "body": "sdfsdf" "image": "http://example.com" } } Using componentWillRecieveProps, this works perfectly for retrieving the title. componentWillReceiveProps(nextProps) { this.setState({ title: nextProps.blog.title, }) } However, I'm having difficulty retrieving the nested fields. When I do this: componentWillReceiveProps(nextProps) { console.log("new title is", nextProps

问题 Hello i use Immuteble Map for state and when i try maspStateToProps i have this error. Uncaught Invariant Violation: mapStateToProps must return an object. Instead received Map {}. Here is my code: Component: const mapStateToProps = (state) => { return state } class LoanCalculator extends React.Component{ componentWillMount(){ this.dispatch(loadConstraints()); } render(){ return ( <div> <h1> Loan Calculator </h1> <SlidersBox {...this.props}/> </div> ) } } LoanCalculator = connect(

问题 Hello i use Immuteble Map for state and when i try maspStateToProps i have this error. Uncaught Invariant Violation: mapStateToProps must return an object. Instead received Map {}. Here is my code: Component: const mapStateToProps = (state) => { return state } class LoanCalculator extends React.Component{ componentWillMount(){ this.dispatch(loadConstraints()); } render(){ return ( <div> <h1> Loan Calculator </h1> <SlidersBox {...this.props}/> </div> ) } } LoanCalculator = connect(

问题 I have been trying to learn how to better structure my Redux stores and stumbled upon this lesson by Dan. https://egghead.io/lessons/javascript-redux-normalizing-the-state-shape#/guidelinesModal Although I understand how to go about normalizing my data in this way, I do not understand the motivation behind it. Particularly, I have two questions. Why wont simple arrays be sufficient? Dan mentions - "In complex apps, we might have more than a single array and todos with the same IDs in

问题 In the getting started video of Redux we see that the Footer (a dumb component) uses Filterlink (a container). But when I read this article, it seems, but not very clearly, that only containers should use/render containers. For me, if Footer uses Filterlink (which is tied to Redux) I can't reuse it on other projects which don't use Redux. But maybe it is an exception? Maybe hard coding dumb component for use only on one project is ok? Am I missing something? 回答1: The article was somewhat out

问题 In the Redux examples, the syntax used is: const App = () => ( <div> <AddTodo /> <VisibleTodoList /> <Footer /> </div> ) I was toying around with a new example app and mistyped the above code with curly brackets instead of parentheses like so: const App = () => { <div> <AddTodo /> <VisibleTodoList /> <Footer /> </div> } I console logged both of the following and the result seemed to be the same. My question is what is the difference between these 2 and why does React like the parentheses but

问题 I am working on a React/Redux application that allows for "widgets" to be added to a page and manipulated in 2D space. It is a requirement that multiple widgets can be selected and manipulated at once. A simplified version of my current state tree looks something like the following... { widgets: { widget_1: { x: 100, y: 200 }, widget_2: { x: 300, y: 400 }, widget_3: { x: 500, y: 600 } }, selection: { widgets: [ "widget_1", "widget_3" ] } } I currently have this tree managed by 2 reducers one

问题 I am learning the redux pattern and using ngrx with angular 2. I am creating a sample blog site which has following shape. export interface BlogContent { id: string; header: string; tags: string[]; title: string; actualContent: ActualContent[]; } and my reducer and actions are as following: import { ActionReducer, Action } from '@ngrx/store'; import * as _ from 'lodash'; export interface ActualContent { id: string; type: string; data: string; } export interface BlogContent { id: string;