fix: layout and pagination items overlap#783
Merged
Conversation
de31e09 to
8090eea
Compare
This was referenced Oct 30, 2025
Closed
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
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.
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:
layoutSlot([...])renders in the slots that pagination couldn't reach (due to not enough source)❌ Current behavior:
layoutSlot([...])renders in all slotslayoutSlotSample code:
This PR also removes
layoutSlot('O')restriction.Gravando.2025-08-02.141152.mp4
Gravando.2025-08-02.140331.mp4