You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 7, 2022. It is now read-only.
Have a tree grid that has a single page. Update dataset to have multiple pages. Scroll to other pages. Change dataset back to a dataset that only has 1 page. The grid is stuck in a blank state where it can't render rows because it is on page 2 when only 1 exists.
The variables options.paging.offset does not propagate downward into the data-table controllers at all. Furthermore, pretty much nothing propagates down correctly due to all these custom watchers. The entire component set does not use any angular data propagation at all instead relying on custom watchers.
How do I programmatically change the page? I have created a fork of this component and added custom events to the pager.controller, body.controller, datatable.controller. Nothing works.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Have a tree grid that has a single page. Update dataset to have multiple pages. Scroll to other pages. Change dataset back to a dataset that only has 1 page. The grid is stuck in a blank state where it can't render rows because it is on page 2 when only 1 exists.
The variables options.paging.offset does not propagate downward into the data-table controllers at all. Furthermore, pretty much nothing propagates down correctly due to all these custom watchers. The entire component set does not use any angular data propagation at all instead relying on custom watchers.
How do I programmatically change the page? I have created a fork of this component and added custom events to the pager.controller, body.controller, datatable.controller. Nothing works.
The text was updated successfully, but these errors were encountered: