Meteor-Community-Packages / Meteor-Community-Packages/meteor-tabular
If final records of other than first page deleted, page doesn't change
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 360
- Forks
- 132
- PR merge metrics
- No merged PRs in 30d
Description
Encountered this bug few days ago where if I'm on another page than the first and delete enough records that they all are in the first page, page doesn't change but instead just shows the "No matching records found" message.
For example I have 12 records total and I'm showing only 10 records per page. I move to the second page and delete the two last records so only the 10 records remain. At this point usually table should move me back to the first page which still has the 10 records but instead doesn't move me and just shows "No matching records found" message.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue with 12 records and 10 records per page: navigate to page two, delete its two records, and observe the empty result. Trace the table's pagination and deletion handling; done means the view returns to page one and shows the remaining 10 records instead of "No matching records found."
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100