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
Has there been any thoughts to allowing the BigTreeModule search function to be able to paginate more easily? Similarly to how getPageCount and getPage can be leveraged?
The text was updated successfully, but these errors were encountered:
With the current crazy ordering of parameters to that method, I think sticking page at the end would be... non-ideal. On the other hand, giving it the ability to paginate would be very helpful. I think this might need a refactor in BigTree 5 when we break some backwards compatibility -- BigTreeModule will still stick around but it's likely that module classes will by default extend a different class instead.
I'm going to keep this issue open while I work that out and will give you an update to take a look at the new class to get feedback once it's in a decent state!
Has there been any thoughts to allowing the BigTreeModule search function to be able to paginate more easily? Similarly to how getPageCount and getPage can be leveraged?
The text was updated successfully, but these errors were encountered: