Most people start out by listening to the relevant stores in a controller-view component near the top of the hierarchy. Later, when it seems like a lot of irrelevant props are getting passed down through the hierarchy to some deeply nested component, some people will decided it’s a good idea to let a deeper component … Read more
I don’t see where in the gist that you posted you are doing the redirect. I only see the AUTH_SIGNIN and AUTH_SIGNIN_SUCCESS actions, and they look pretty straightforward. But no, there is no hack to create an action in the middle of a dispatch, and this is by design. Actions are not supposed to be … Read more
React Router v3 This is what I do var Router = require(‘react-router’); Router.browserHistory.push(‘/somepath’); React Router v4 Now we can use the <Redirect>component in React Router v4. Rendering a <Redirect> will navigate to a new location. The new location will override the current location in the history stack, like server-side redirects. import React, { Component } … Read more
Browser technology currently doesn’t support downloading a file directly from an Ajax request. The work around is to add a hidden form and submit it behind the scenes to get the browser to trigger the Save dialog. I’m running a standard Flux implementation so I’m not sure what the exact Redux (Reducer) code should be, … Read more
So my final conclusion on this question is that I didn’t think it through properly. It seemed natural just to pass my data through the Link so I can access them in my Child component. As Colin Ramsay mentioned there is something called state in the Link but that’s not the way to do it. … Read more
Change <button type=”button” to <button type=”submit”. Remove the onClick. Instead do <form className=”commentForm” onSubmit={this.onFormSubmit}>. This should catch clicking the button and pressing the return key. const onFormSubmit = e => { e.preventDefault(); // send state to server with e.g. `window.fetch` } … <form onSubmit={onFormSubmit}> … <button type=”submit”>Submit</button> </form>
I’ve seen the flux pattern implemented both ways, and after having done both myself (initially going with the former approach), I believe that stores should be dumb recipients of data from the actions, and that asynchronous processing of writes should live in the action creators. (Async reads can be handled differently.) In my experience, this … Read more
Axios does not support canceling requests at the moment. Please see this issue for details. UPDATE: Cancellation support was added in axios v0.15. EDIT: The axios cancel token API is based on the withdrawn cancelable promises proposal. UPDATE 2022: Starting from v0.22.0 Axios supports AbortController to cancel requests in fetch API way: Example: const controller … Read more
I’m a big proponent of putting async write operations in the action creators and async read operations in the store. The goal is to keep the store state modification code in fully synchronous action handlers; this makes them simple to reason about and simple to unit test. In order to prevent multiple simultaneous requests to … Read more
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, … Read more