Return it on GET /applications as a top-level array property in an object, e.g. { applications: [ ... ] }. Do not return a top-level array as that makes it impossible to extend the response with metadata (e.g. offset/count in case of pagination).
Pagination, sorting, and filtering is delegated to the client side. If time allows, continue work in #24, #25, #26 to provide the functionality on the server side (note: it wouldn't save much effort on the client side as constructing queries isn't substantially faster than filtering arrays).
Design
GET /applicationsas a top-level array property in an object, e.g.{ applications: [ ... ] }. Do not return a top-level array as that makes it impossible to extend the response with metadata (e.g. offset/count in case of pagination).Pagination, sorting, and filtering is delegated to the client side. If time allows, continue work in #24, #25, #26 to provide the functionality on the server side (note: it wouldn't save much effort on the client side as constructing queries isn't substantially faster than filtering arrays).