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
We want to implement pagination in the list / get endpoints for our API, namely the reviews, roles, and companies routers.
I think it would be a good idea to add the pagination inputs into the context of the procedure itself. It would look something like this (definitely not chat gpt):
We can either make a new pagination procedure or implement it into the current public procedure. Whichever you like works, doesn't matter since they are optional and don't have to be used in irrelevant endpoints. Then you can access these in the ctx of each endpoint that requires them. See https://orm.drizzle.team/docs/guides/limit-offset-pagination for how to integrate them into our drizzle queries
Conditions of Satisfaction:
Some abstracted pagination logic procedure (new or implement into public procedure)
Existing endpoint calls from the frontend don't go up in flames
Pagination actually works lol
Let me know if you need help
The text was updated successfully, but these errors were encountered:
We want to implement pagination in the list / get endpoints for our API, namely the reviews, roles, and companies routers.
I think it would be a good idea to add the pagination inputs into the context of the procedure itself. It would look something like this (definitely not chat gpt):
We can either make a new pagination procedure or implement it into the current public procedure. Whichever you like works, doesn't matter since they are optional and don't have to be used in irrelevant endpoints. Then you can access these in the
ctx
of each endpoint that requires them. See https://orm.drizzle.team/docs/guides/limit-offset-pagination for how to integrate them into our drizzle queriesConditions of Satisfaction:
Let me know if you need help
The text was updated successfully, but these errors were encountered: