Picker Pagination #60

New issue

Open

opened 2026-02-08 11:19:23 -06:00 by noe.trevino · 0 comments

noe.trevino commented

2026-02-08 11:19:23 -06:00

Owner

Problem

When dealing a picker with a lot of potential items (mainly the child and parent pickers) there is a possibility of the picker 'overflowing'
off to 'infinity'.

Solution

We need to add pagination to ALL the pickers. We can leverage the current dynamicDimenstions to decide the page size.

Technical Notes

Note: C-[ cant be a hotkey, it is the code for escape.

Thoughts:
How will users scroll through pages?
Can we encapsulate the logic into a Paginator struct, and extract all picker components into a PaginatedPicker interface, and have a methods like show, NextPage, PrevPage, etc...
Basically, this is going to be a A LOT of the same shit in the code. We can afford some indirection here

## Problem When dealing a picker with a lot of potential items (mainly the child and parent pickers) there is a possibility of the picker 'overflowing' off to 'infinity'. ## Solution We need to add pagination to ALL the pickers. We can leverage the current `dynamicDimenstions` to decide the page size. ## Technical Notes Note: C-[ cant be a hotkey, it is the code for escape. Thoughts: How will users scroll through pages? Can we encapsulate the logic into a `Paginator` struct, and extract all picker components into a `PaginatedPicker` interface, and have a methods like `show`, `NextPage`, `PrevPage`, etc... Basically, this is going to be a A LOT of the same shit in the code. We can afford some indirection here

noe.trevino added the

priority

size

labels

2026-09-29 13:35:19 -05:00