You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
feat: [BE] Add pagination to published components endpoint #179
The GET /api/published_components/ endpoint currently returns all components with no pagination. There are existing TODO comments in the code acknowledging this:
changed the title [-]feat: Add pagination to published components endpoint[/-][+]feat: [BE] Add pagination to published components endpoint[/+]on Mar 19, 2026
How many components are being returned now? Under 100 currently.
Do we expect N times growth in the upcoming weeks? Honestly not sure — it's possible. Pinging @Ark-kun for his take on expected growth.
Can the UI mitigate this in the meantime? Likely yes — we could implement front-end pagination over the full returned list as a stopgap. That said, if the component count does grow significantly it won't scale well, which is part of the motivation for doing this properly on the backend.
Curious what's driving the skepticism — is it the assumption that component counts will stay small enough to make a full total_count cheap? How many components are we realistically expecting over time?
@Mbeaulne i think this is a good candidate for my goal of creating an experimental API in oasis-backend. I will need to 1) create a design doc and review it with the team and then 2) implement it. Curious how urgent are you wanting this feature. My thought is might have an release by mid April if everything goes smoothly.
Activity
[-]feat: Add pagination to published components endpoint[/-][+]feat: [BE] Add pagination to published components endpoint[/+]yuechao-qin commentedon Mar 19, 2026
Just trying to get a sense of priority / urgency:
Ark-kun commentedon Mar 19, 2026
Agreed.
I'm a bit skeptical here.
Mbeaulne commentedon Mar 23, 2026
Good questions — here's where things stand:
Mbeaulne commentedon Mar 23, 2026
Curious what's driving the skepticism — is it the assumption that component counts will stay small enough to make a full
total_countcheap? How many components are we realistically expecting over time?yuechao-qin commentedon Mar 25, 2026
@Mbeaulne i think this is a good candidate for my goal of creating an experimental API in oasis-backend. I will need to 1) create a design doc and review it with the team and then 2) implement it. Curious how urgent are you wanting this feature. My thought is might have an release by mid April if everything goes smoothly.