New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Getting only one sort and one filter event after changing the state of grid using setState function #8064

Closed

gwozt opened this issue Aug 31, 2020 · 9 comments

Assignees

Labels

grid: general grid: state-persistence 🆕 status: new status: inactive 🧰 feature-request

gwozt commented Aug 31, 2020 •

edited

Loading

Everytime I change the state of a grid using setState function I get as many filter and sort events as the total number of columns of that grid. This becomes a huge problem when I use remote data fetching strategies, where my back-end receives so many unnecessary data fetching requests.

I would like to have only one sort and one filter event fired after changing the state, which should contain all the sort and filter parameters a state had at the time of saving.

gwozt added the 🧰 feature-request label

ig-bot bot added the 🆕 status: new label

zdrawku assigned hanastasov

hanastasov assigned zdrawku

zdrawku added grid: general grid: state-persistence labels

github-actions bot commented Dec 9, 2020

There has been no recent activity and this issue has been marked inactive.

github-actions bot added the status: inactive label

hanastasov removed the status: inactive label

github-actions bot commented Mar 30, 2021

There has been no recent activity and this issue has been marked inactive.

github-actions bot added the status: inactive label

github-actions bot closed this as completed

zdrawku reopened this

github-actions bot closed this as completed

hanastasov removed the status: inactive label

hanastasov reopened this

github-actions bot commented Sep 27, 2021

There has been no recent activity and this issue has been marked inactive.

github-actions bot added the status: inactive label

hanastasov removed the status: inactive label

github-actions bot commented Nov 27, 2021

There has been no recent activity and this issue has been marked inactive.

github-actions bot added the status: inactive label

hanastasov removed the status: inactive label

github-actions bot commented Jan 29, 2022

There has been no recent activity and this issue has been marked inactive.

github-actions bot added the status: inactive label

github-actions bot closed this as completed

hanastasov removed the status: inactive label

zdrawku reopened this

github-actions bot commented May 28, 2022

There has been no recent activity and this issue has been marked inactive.

github-actions bot added the status: inactive label

github-actions bot closed this as completed

zdrawku reopened this

zdrawku removed the status: inactive label

github-actions bot commented Sep 5, 2022

There has been no recent activity and this issue has been marked inactive.

github-actions bot added the status: inactive label

hanastasov removed the status: inactive label

github-actions bot commented Nov 7, 2022

There has been no recent activity and this issue has been marked inactive.

github-actions bot added the status: inactive label

hanastasov removed the status: inactive label

github-actions bot commented Jan 7, 2023

There has been no recent activity and this issue has been marked inactive.

github-actions bot added the status: inactive label

github-actions bot closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment