Pagination on Curbs endpoints #62
Replies: 4 comments 6 replies
-
See this discussion @zanebclark. Welcome your thoughts. |
Beta Was this translation helpful? Give feedback.
-
Hi folks, long time listener first time commenter :) I'd prefer to keep one endpoint to one type of object, i.e. If we do have a need to keep both objects in one endpoint, a few thoughts:
|
Beta Was this translation helpful? Give feedback.
-
I agree strongly with @joeb1415's point that endpoints should only return one type of data object. |
Beta Was this translation helpful? Give feedback.
-
Well I can see your point @jiffyclub and @joeb1415, but this configuration has been there for a few months and we are about to launch. We will have to go back and look at the meetings and reasoning about why they are in the same endpoint. I recall some strong feelings about having all policy and curb data in a single endpoint, and not split across two of them. A change may have to wait for the next release. |
Beta Was this translation helpful? Give feedback.
-
The query and fetch endpoints for /curbs/zone return 2 data objects, zones and policies.
Since these endpoints can be paginated, how should pagination be handled? What is the best practice method? Should all curbs data be returned first, then policies data? Or should it be split evenly as much as possible?
How you handle keeping state when returning data across multiple endpoint pages?
Beta Was this translation helpful? Give feedback.
All reactions