Using setState in afterColumnFilter function

It will crash program after I use setState in afterColumnFilter.

getFilterResult = (f, result) => {
    Promise.resolve(this.somethingComputing(result))
                  .then(data => this.setState({data: data}))
}

render(){
   const options = {
       afterColumnFilter: this.getFilterResult
   }
}

It will call setState many time…

[Terryhung]

@AllenFang Doing some computing for data.

Do you have any suggestion for us to achieve this goal?

[garrettmurphy]

@AllenFang I have a use case for you.

We have been working with react-bootstrap-table v4.0.0-beta.1. We had issues with users of our app selecting multiple rows, then choosing to filter the rows. If they did this, the rows remained selected that were now no longer visible, and if they executed an action on the visible rows that were selected, it would also execute on the rows hidden by the filter.

To avoid this, we have an afterColumnFilter function that sets a property in state, currentFilteredData, storing a record of all the visible selected rows so we only execute commands on those rows.

Now that we are attempting to upgrade to 4.2.0, it’s an infinite loop, as others have experienced. We can store the filter conditions and do a comparison, only setting the state if the conditions have changed, but this seems like a bad workaround for a breaking change.