In order to use await, the function directly enclosing it needs to be async. According to your comment, adding async to the inner function fixes your issue, so I’ll post that here: Possibly, you could remove the async from the outer function because it does not contain any asynchronous operations, but that would depend on … Read more
Full code here: https://gist.github.com/js08/0ec3d70dfda76d7e9fb4 Hi, I have an application where it shows different templates for desktop and mobile on basis of build environment. I am successfully able to develop it where I need to hide the navigation menu for my mobile template. right now I am able to write one test case where it fetches … Read more
Per the Redux FAQ question at here, this.props.dispatch is available by default if you do not supply your own mapDispatchToProps function. If you do supply a mapDispatchToProps function, you are responsible for returning a prop named dispatch yourself: Or, you can make sure your action creators are pre-bound using Redux’s bindActionCreators utility, and skip having to worry about using this.props.dispatch in your component.
npm start runs a script that the app maker built for easy starting of the app npm install installs all the packages in package.json run npm install first then run npm start
Redux author here! Redux is not that different from Flux. Overall it has same architecture, but Redux is able to cut some complexity corners by using functional composition where Flux uses callback registration. There is not a fundamental difference in Redux, but I find it makes certain abstractions easier, or at least possible to implement, that would … Read more
I suspect that the problem lies in the fact that you are calling your state setter immediately inside the function component body, which forces React to re-invoke your function again, with the same props, which ends up calling the state setter again, which triggers React to call your function again…. and so on. Instead, I … Read more
As Context is no longer an experimental feature and you can use Context in your application directly and it is going to be great for passing down data to deeply nested components which what it was designed for. As Mark Erikson has written in his blog: If you’re only using Redux to avoid passing down props, context could … Read more
Q: Is this ok?A: yes Q: Is this expected?Yes, this is expected (if you are using react-redux). Q: Is this an anti-pattern?A: No, this is not an anti-pattern. It’s called “connecting” your component or “making it smart”. It’s by design. It allows you to decouple your component from your state an additional time which increases the modularity of … Read more
I feel like none of the answers have crystallized why mapDispatchToProps is useful. This can really only be answered in the context of the container-component pattern, which I found best understood by first reading:Container Components then Usage with React. In a nutshell, your components are supposed to be concerned only with displaying stuff. The only place they are supposed to get information from is … Read more