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 }}
This repository has been archived by the owner on Aug 26, 2022. It is now read-only.
For customer management, it'd be useful to extend the functionality of the GET /customers endpoint.
Consider having GET /customers return a paginated list of results. My immediate need is for the sort order to be by date created.
For any paginated response, it's useful to know when you've hit the end of the series by either having the total count in the response or a marker on the response to signal the end.
We could do this in all sorts of ways, but typical REST might be something like
GET /customers?orderBy=createdAt&orderDirection=desc&limitTo=50
Also related, filtering the list of customers by status and createdAt (before or after), would be a solid start.
The text was updated successfully, but these errors were encountered:
@jmbrown412 can we include a filter for type that returns only individual or business Customers if specified. It was on #99 but I don't think we've gotten to it yet.
Related to #99
For customer management, it'd be useful to extend the functionality of the GET /customers endpoint.
Consider having
GET /customers
return a paginated list of results. My immediate need is for the sort order to be by date created.For any paginated response, it's useful to know when you've hit the end of the series by either having the total count in the response or a marker on the response to signal the end.
We could do this in all sorts of ways, but typical REST might be something like
GET /customers?orderBy=createdAt&orderDirection=desc&limitTo=50
Also related, filtering the list of customers by
status
andcreatedAt
(before or after), would be a solid start.The text was updated successfully, but these errors were encountered: