Contributes to #941
For pagination we need to have a endpoint, that fetches the rows of a table or view also in consideration of user supplied filter and sorting rules.
The current controller methods of \OCA\Tables\Controller\Api1Controller (indexTableRows and indexViewRows) accept parameters for pagination, but that is it.
In this context it makes sense to integrate the approaches of #927 and create a new v2 endpoint.
The current v1 endpoint shall be deprecated, as it is already not used by the web frontend. It should not be removed (the android app might make use of it – needs to be verified).
The internal endpoints (\OCA\Tables\Controller\RowController::index() and ::indexView()) shall be deprecated, and later on removed as soon as the web interfaces also switches to the v2 endpoint.
Contributes to #941
For pagination we need to have a endpoint, that fetches the rows of a table or view also in consideration of user supplied filter and sorting rules.
The current controller methods of
\OCA\Tables\Controller\Api1Controller(indexTableRowsandindexViewRows) accept parameters for pagination, but that is it.In this context it makes sense to integrate the approaches of #927 and create a new v2 endpoint.
The current v1 endpoint shall be deprecated, as it is already not used by the web frontend. It should not be removed (the android app might make use of it – needs to be verified).
The internal endpoints (
\OCA\Tables\Controller\RowController::index()and::indexView()) shall be deprecated, and later on removed as soon as the web interfaces also switches to the v2 endpoint.