Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

The problem with pagination in the data table

See original GitHub issue

Steps to reproduce

Create a component within which there will be a data table Add the pagination option

Versions

What is expected ?

pops pagination must auto-fill some default options, like as rowsPerPage. This is the case if the data table is native screenshot_20170530_145640

What is actually happening ?

User data completely replaces the standard value. Because of what the table does not display information. This is the case if the data table is in another component screenshot_20170530_145846 As a consequence of the field, pageStart and pageStop are NaN screenshot_20170530_150117 This leads to the fact that all elements are filtered out in filteredItems

Reproduction Link

https://codepen.io/cawa-93/pen/qmzpZW?editors=1010

Issue Analytics

State:
Created 6 years ago
Comments:14 (12 by maintainers)

Top GitHub Comments

2reactions

nekosaurcommented, May 30, 2017

This is not a bug with the data table component. It’s simply a fact of life when using the .sync modifier. You must emit an update event in your component when the data table changes the pagination, since in your component, pagination is simply a prop which you can’t modify directly.

See here for a solution https://codepen.io/anon/pen/GmbwZa

0reactions

lock[bot]commented, Apr 16, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. Please direct any non-bug questions to our Discord