Skip to content

fix: layout and pagination items overlap#783

Merged
devnatan merged 9 commits intomainfrom
fix/pagination-availableslot
Aug 2, 2025
Merged

fix: layout and pagination items overlap#783
devnatan merged 9 commits intomainfrom
fix/pagination-availableslot

Conversation

@devnatan
Copy link
Copy Markdown
Owner

@devnatan devnatan commented Aug 2, 2025

Fixes layout and pagination items overlap. The use case is: when you need to render the "empty slots" of pagination with a placeholder item. Currently this is not possible but it is not the indeed behavior.

Create a pagination using some character as layout target then use layoutSlot(<the same character>).

Expected behavior:

  1. Pagination renders first
  2. layoutSlot([...]) renders in the slots that pagination couldn't reach (due to not enough source)
  3. Changing pages only affects Pagination

Current behavior:

  1. layoutSlot([...]) renders in all slots
  2. Pagination renders "below" (IF supports Overlapping Items so there's a "above"/"below" concept) layoutSlot
  3. Changing pages only affects Pagination

Sample code:

State<Pagination> paginationState = buildLazyPaginationState([...])
    .layoutTarget('#')
    .build()

// onFirstRender
render.layoutSlot('#', [...placeholderItem]);

This PR also removes layoutSlot('O') restriction.

Before After
Gravando.2025-08-02.141152.mp4
Gravando.2025-08-02.140331.mp4

@devnatan devnatan force-pushed the fix/pagination-availableslot branch from de31e09 to 8090eea Compare August 2, 2025 17:28
@devnatan devnatan self-assigned this Aug 2, 2025
@devnatan devnatan merged commit 666102c into main Aug 2, 2025
3 of 5 checks passed
@devnatan devnatan deleted the fix/pagination-availableslot branch August 2, 2025 17:35
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