Skip to content

fix(postgrest-swr): preserve pagination controls during revalidation#696

Open
psteinroe wants to merge 1 commit into
mainfrom
fix/pagination
Open

fix(postgrest-swr): preserve pagination controls during revalidation#696
psteinroe wants to merge 1 commit into
mainfrom
fix/pagination

Conversation

@psteinroe

Copy link
Copy Markdown
Owner

This updates the PostgREST SWR pagination and infinite-scroll hooks so navigation controls stay available while already-loaded data is being revalidated. It also makes those controls disappear only when a newly requested page has not finished loading yet, which prevents duplicate pagination actions against incomplete state.

Behavior change: nextPage, previousPage, and loadMore are no longer gated by isValidating alone. They now remain usable for stale-but-loaded data and are hidden only when the requested page for the current size/index is not yet present.

API change: useInfiniteOffsetPaginationQuery now exposes hasNextPage and hasPreviousPage booleans so consumers can read pagination availability without inferring it from the presence of callback helpers.

The docs were updated to clarify the new control semantics, and new unit tests cover the stale-data and unloaded-page cases for both offset and cursor-based hooks.

@changeset-bot

changeset-bot Bot commented May 6, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: c0160ae

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@supabase-cache-helpers/postgrest-swr Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@codecov

codecov Bot commented May 6, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.71%. Comparing base (ccfaaca) to head (c0160ae).
⚠️ Report is 4 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##           main     #696       +/-   ##
=========================================
+ Coverage      0   92.71%   +92.71%     
=========================================
  Files         0      151      +151     
  Lines         0     2415     +2415     
  Branches      0      763      +763     
=========================================
+ Hits          0     2239     +2239     
- Misses        0      145      +145     
- Partials      0       31       +31     
Flag Coverage Δ
postgrest-core 92.71% <100.00%> (?)
postgrest-react-query 92.71% <100.00%> (?)
postgrest-server 92.71% <100.00%> (?)
postgrest-swr 92.71% <100.00%> (?)
storage-core 92.71% <100.00%> (?)
storage-react-query 92.71% <100.00%> (?)
storage-swr 92.71% <100.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant