Skip to content
This repository was archived by the owner on Sep 30, 2024. It is now read-only.
This repository was archived by the owner on Sep 30, 2024. It is now read-only.

[Meta] FE scale audit: Reusable patterns for proper cursor-based pagination #44706

@philipp-spiess

Description

@philipp-spiess

We’re working on a replacement for useConnection with better defaults and support for bi-directional pagination. The existing useConnection hook was added as a replacement for a bit over a year ago and is a drop-in replacement for the older pattern on the frontend (without having to change anything in the backend). It does this very well: It’s currently simple to move from to the new hook implementation.

As part of the strategic scale-testing, I’m currently working with Naman and Kelli take this one step further: We’re rethinking how we’re doing pagination across the stack. This means that we now recommend a fully cursor-based implementation in the backend that supports traversal in both directions and we’re also changing the UI default from being an append-only list to showing individual pages. This will need new front-end components: a hook similar to useConnection and a new pagination UI component and new back-end components.

Plan

This issue tracks the high-level completion of this effort and is broken down into the following tasks:

Read more

Learn more on why cursor-based navigation is the new preferred way or why we following the Relay spec for cursor based navigation:

/cc @felixfbecker

Metadata

Metadata

Type

No type
No fields configured for issues without a type.

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions