Detailed explanation of how to use take in redux-saga

This article mainly introduces the detailed explanation of how to use take in redux-saga. Now I will share it with you and give you a reference.

This article introduces a detailed explanation of the use of take in redux-saga and shares it with everyone. The details are as follows:

Bring me an API usage method that I have studied for a long time.

redux -The way to use the take API in effect in saga is call, put, and select. However, there is really no chance to use take, and I don’t know where to use it. Anyway, since it is redux- Written by saga, there must be its usage. Regardless of 37 21, learn how to use it first.

Let’s take a look at the introduction first:

take

The performance of take Like takeEvery, it monitors an action, but unlike takeEvery, it does not respond every time the action is triggered, but only responds to the action when the take statement is executed in the execution sequence.

When using the take statement in the genetator to wait for an action, the generator is blocked, waiting for the action to be distributed, and then continues execution.

takeEvery just listens to each action and then executes the processing function. takeEvery has no control over when and how to respond.

But take is different. We can decide in the generator function when to respond to an action and what to do after an action is triggered.

The biggest difference: take will only respond to the corresponding action when the execution flow is reached, while takeEvery will respond to the action once registered.

The above code:

effects: {
 * takeDemo1({payload}, {put, call, take}) {

 },
 * takeInputChange({payload}, {put, call, take,takeEvery,takeLatest}) {
  // yield call(delay,1000);
  console.log(takeEvery);
  // for (let i = 0; i < 3; i++) {
   const action = yield take(&#39;takeBlur&#39;});
   console.log(action, &#39;action&#39;);
   console.log(payload.value);
  // }

 },
 * takeBlur() {
  console.log(323)
 },
}

changeHandle(e){
 this.props.dispatch({type:'takeInputChange',payload:{value:e.target.value}})
}
blur(){
 this.props.dispatch({type:'takeBlur'})
}
render() {

 return (
  <p style={{position: &#39;relative&#39;}}>
   <Input onChange={this.changeHandle.bind(this)} onBlur={this.blur.bind(this)}/> 
  </p>
  )
}

There is an input on the page, bound to two methods, the first is the onchange method, the other is the onBlur method,

When the input value When changing, this function is called through this.props.dispatch({type:'takeInputChange'}), but because the take method is encountered, execution cannot continue (paused). If the take here is replaced by takeEvery is quite different. The function will continue to execute, that is, the following two consoles will execute,

and the method of takeEvery execution is placed in its callback, see the following code

yield takeEvery('takeBlur',()=>{console.log(payload.value)});

What needs to be emphasized is that this function will be triggered every time the input changes, so every time it changes, you will see that the console will print the value in the console.

Next, if the input loses focus, The onBlur method will be executed, and this.props.dispatch({type:'takeBlur'}) is called at this time;

Because the take in takeInputChange has monitored the takeBlur action, it will continue to execute what needs to be executed. Content.

This take has been studied for a long time anyway. I don’t know when this thing will be useful.

The above is what I compiled for everyone. I hope it will be useful in the future. Everyone is helpful.

Related articles:

Explain in detail the practical skills in Immutable and React

How to solve the compatibility of easyui date and time box ie Practical problems (detailed tutorial)

Using Native in React to implement image viewing components

The above is the detailed content of Detailed explanation of how to use take in redux-saga. For more information, please follow other related articles on the PHP Chinese website!