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.
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
Server side integration with redux #1751
Comments
We're using Redux in our application with ag-grid. We use the infinite scroll model (though in pagination mode) and we currently don't use any dispatch actions to get data. We just directly fetch in the I don't think it's "hacky' to dispatch redux actions on grid events, if you're using a react-redux and the |
We are currently writing a Redux-based Angular application in which we want to use the infinite scroll model of ag-grid (we currently use ag-grid simply in the deltaRowDataMode, but will need infinite scroll in a few cases). As @cliffsun91 said, I think the only practical way to do that right now is to not store your rows in Redux state, but rather have your ag-grid data source directly query the api. However, this would be a break from our usual architecture pattern. It would be super nice if ag-grid had a way to store the infinite scroll state within a reducer so we could store the component's state in a manner that is much more accessible as well as consistent with Redux architecture patterns. |
Hi, Thank you for raising this issue for us, at this moment we are reviewing how we process Feature Requests/questions that come through from GitHub. As I am sure you are aware, we offer two products: ag-Grid - this is entirely free to use in line with our MIT license We currently have a very full pipeline of work which can be viewed here: https://www.ag-grid.com/ag-grid-pipeline/ This will be our priority for the coming months and as a result, we don’t have capacity to take feature requests/questions from GitHub, but you might find that yours has already been raised in our pipeline. We will do a periodic review of GitHub issues for any bugs raised and these can also be tracked on our pipeline page. Thanks for your understanding. |
Hello everybody, |
@omriye did you find any solution I am stuck with the same issue |
@MalkaGloiberman unfortunately not, it is simple not supported. The compromise is to leave redux out of the pagination and to perform direct api calls with "async ... await", in order to retrieve the next data chunk. |
after about 5 years from the discussion stared I dont think you fixed the issue could you just make it like this in server side render
|
I'm submitting a ... (check one with "x")
Current behavior
The example with redux is great, but only with "In Memory" row model.
What is the motivation / use case for changing the behavior?
Using infinite scroll, we could use
getRows
and dispatch there, butsuccessCallback
andfailCallback
doesn't make sense in this case.The "In Memory" row model is almost good enough if we want to load data on the fly, but listening to grid events to dispatch redux action seems a bit too "hacky".
Maybe introduce a new row model for Redux ?
The text was updated successfully, but these errors were encountered: