Fix invalid empty-state range in getShowingInfo() - #21
Merged
Conversation
Copilot
AI
changed the title
[WIP] Fix invalid empty-state range in getShowingInfo
Fix invalid empty-state range in getShowingInfo()
Jul 18, 2026
RA9
marked this pull request as ready for review
July 18, 2026 13:03
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
getShowingInfo()always computedstartIndex = 1, producing"Showing 1 to 0 of 0 items"when data was empty. The fix returns"No items to show"early whentotalItems === 0, before any index arithmetic runs.Changes
src/index.ts: IngetShowingInfo(), short-circuit with"No items to show"whentotalItems === 0— applies to both normal and filtered data modes.src/__tests__/index.test.ts: New test covering the empty-data case.