Add pagination foundations#885
Draft
jpurnell wants to merge 1 commit into
Draft
Conversation
…omponent Introduces pagination support for Ignite: - Paginator<Content> generic type for slicing collections into pages - PaginationContext for tracking page state and generating page URLs - Pager component rendering Bootstrap 5 pagination controls with three styles: prevNext, numbered, and compact (with ellipsis) Purely additive. Environment key integration and PaginatedPage protocol are planned as follow-ups.
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
1 participant
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.
Summary
Paginator<Content>type for slicing collections into pagesPaginationContextfor tracking page state and generating URLsPagercomponent rendering Bootstrap 5 pagination controls with three styles: prevNext, numbered, and compact (with ellipsis)Design
Purely additive — all new files.
PageracceptsPaginationContextas an explicit parameter rather than using@Environment, making it usable immediately without framework changes. Environment key integration andPaginatedPageprotocol are planned as follow-ups.Test plan
swift buildclean with no warnings