Replies: 2 comments 5 replies
-
Fully agree. Pagination only when it makes sense The UI only needs:
API languageIMHO, The REST API should talk in its own "language". It means, to use UI LanguageThe UI takes the REST API "language" and translates it to human "language" so the UI will translates This way both UI and API are clearly separated |
Beta Was this translation helpful? Give feedback.
-
Just tidying up, do we consider this discussion "resolved"? |
Beta Was this translation helpful? Give feedback.
-
Coming from a discussion on #82 … I think we need to define how "pagination" works.
As a goal, I think it makes sense to leverage the same logic/struct of pagination for all APIs. Re-using code as good as possible. But not forcing pagination on all APIs. Only if it makes sense.
While we have a current definition of pagination on the backend, I personally thinks it's a bit verbose. Then again, I don't have a strong opinion other than: please let's re-use the same logic for all APIs.
I think the minimum information we need is:
limit
/offset
, orpage_size
/page
.page_size
/page
out of the box, but I am sure we can implement other patterns as wellnumber_of_items
orpage_size
/number_of_pages
.Of course we can add more.
@carlosthe19916 As I think the UI is the most important component working with this, what's your preference?
Beta Was this translation helpful? Give feedback.
All reactions