Fix: Feature usage chart pagination #1013
Open
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.
Background:
When backfilling usage data, the feature usage chart displayed only a few data points, not the complete set. Network inspection revealed that multiple pages of data were successfully retrieved.
Repro:
Solution:
This change aligns the feature usage chart pagination with the feature support chart's implementation:
webstatus.dev/frontend/src/static/js/components/webstatus-feature-page.ts
Lines 621 to 650 in b84a9ac
Testing:
Comprehensive unit tests will be included with the refactor outlined in #964.
To validate the pagination logic, this commit increases the number of data points displayed to over 100, enabling testing through Playwright. To optimize Playwright test performance, the initial data load specifically filters for the feature used in the feature page test, mitigating delays associated with loading excessive fake data.
Other changes