flux

问题 Facebook says that I should not keep a React component in its parent's state. Instead I should be recreating the child in render method each time it is run. What Shouldn't Go in State? React components: Build them in render() based on underlying props and state. Now my question is: How can I do that? Is it even possible? Isn't the state lost if I recreate a child component from scratch? The only way I can think of that this scenario will work in, is that there's only one state object and it

问题 I've read in several places now that accessing state in action creators is an anti-pattern. Dan Abramov has said In general accessing state in action creators is an anti-pattern and you should avoid this when possible. I have recently found myself in the following situation. I have 2 reducers : currentUser: { currentUserId: 'abc' } allUsers { byId: { { abc: { name: "John" age: 21 } def: { name: "Dave" age: 51 } ghi: { name: "Gunners" age: 98 } } }, allIds : ['abc','def','ghi'] //this is a

问题 Since the update flux to 9.0.1 I need to update the colPos of elements. This works fine: UPDATE `tt_content` SET colPos = ((tx_flux_parent * 100) + 11) WHERE tx_flux_column = "content"; But I need also to update the localized content elements. It have in tx_flux_parent the localized parent uid. But I need the parent uid of the standard language. I need to get the value "tx_flux_parent" in tt_content by l18n_parent. So I'm trying to build a query with l18n_parent like this: UPDATE `tt_content`

问题 I've made a TYPO3-Installation 6.2.9 with Fluid powered TYPO3 - the first steps with the Pre-configured Distribution "Site" were fine. My Site/Page-Template is installed and I added all the TypoScript stuff. Now I want to use FLUIDCONTENT (FCE) with FLUX. I've added a new Template-File TeaserOne.html and I try to use the Layout from the Distribution Content.html . Now I can see and write into my input-fields in Backend, but I've no Output in Frontend?! What else do I need? I only see the

问题 I'm writing a Registration Form Component. When form submits it triggers a create user action. createUser actions creates a new user via an ajax api call. If a user already exist, triggered user action fails. We know we cannot return a response from an ajax call, we need a callback for that. How do i tell me component that a user already exists? // Register From Component var Register = React.createClass({ saveUser : function(event){ event.preventDefault(); userActions.createUser(this.state

问题 Short question: It looks like the state of an app can be serialized completely from a React/Flux store. I've seen this with input values and other stuff, but what is with animations or hover effects? Should I use a classic :hover CSS selector for hover effects or should I use mouseenter and -leave events and save hover states in my store? 回答1: If your hover effects are small, like pointer on cursor, etc., I would use mostly CSS. If you want to do bigger DOM manipulations I would use React .

问题 I need to trigger a synchronous action after react-router push, which appears to be async Is it possible to do something like: dispatch(push('/', callbackFunction)) I don't see anything in the react-router docs about a callback to push , which seems quite odd... 回答1: As it seems, push is not asynchronous since it is just an action creator (factory pattern). So you could trigger you actions like this: dispatch(push('/')); dispatch(otherAction()); Relevant lines 来源： https://stackoverflow.com

问题 In Flux , what is the point of using actions , instead of just letting the component publish directly to the dispatcher ? What is it that I can't do without actions ? 回答1: The action creators decouple the component from the dispatcher. You could replace the dispatcher and related pieces with something else and the components would not need to change. 来源： https://stackoverflow.com/questions/29677779/react-flux-whats-the-point-of-actions

问题 Here's my situation, I'm very new to react/flux, and just started to play around with it. My toy project is a simple library app. My current state is as follows: i have a component called Login. This component is responsible only to store the currently "logged in" user to be able to deal with latter Borrow/Return buttons in the library. So the user inputs it's name which will be saved into session storage at the moment. my another component is called Library which holds the main logic of my

问题 I would like to pass router params into Vuex actions, without having to fetch them for every single action in a large form like so: edit_sport_type({ rootState, state, commit }, event) { const sportName = rootState.route.params.sportName <------- const payload = {sportName, event} <------- commit(types.EDIT_SPORT_TYPE, payload) }, Or like so, edit_sport_type({ state, commit, getters }, event) { const payload = {sportName, getters.getSportName} <------- commit(types.EDIT_SPORT_TYPE, payload) }