Just paginating on in memory data is a bit limiting, the caller should probably deal with pagination (data and/or visual); a better pagination interface (arrow function) should be provided and pagination enabled can be deduced by whether this field/property is set or not.

Sorry for this late response on the PR;

I agree that an exposed paginationFilter property, where the consumer / parent component decides what rows to show,
would be a nice addition. It would enhance flexibility and control. However, I would keep the additional enable property,
as there are more configuration options, such as setting the amount of rows per page.

Instead of implementing this functionality now, I suggest to create a new issue for this.
I'd rather have this simple fix merged first, and work on that later 😉

@richturner @DonWillems