When quering collections of data (GetList) in our WebAPI, we do not control the page size of the data to be retrieved, i.e. if someone said per-page=1000000 then we'd return up to 1000000 entities in our response. That would be good if we can introduce (configurable) limits on the data page size for List queries.

Also, if this logic is implememtned, we need to let customers know, what was the real page size used versus the one they asked for. For these purposes we can either adjust the existing PagedList response or return additional information in the response headers:

X-Pagination-Per-Page,
X-Pagination-Total-Count,
X-Pagination-Page-Count,
X-Pagination-Current-Page

cc @fabiomaistro @dcsl-alexis

The API version is selected from the top right dropdown on Swagger, but the required "version" parameter must be entered manually.

Setting options.SubstituteApiVersionInUrl = true; in services.AddVersionedApiExplorer of WebApi's Program.cs will allow Swagger to understand how to fill in the parameter.

I have code ready to push, but need to get authorised ... I'm new to contributing on git-hub!

There is some potentially redundant code - someone should go through and check.

src/OneBeyondStudio.Obelisk.WebUI/src/js/grids/syncfusionGrid/commonDataAccessors.ts

Seems like an initial candidate.

Lots of the code is still in dcslcomponents and refers to DCSL everywhere.