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
Copy file name to clipboardExpand all lines: docs/api-guide/pagination.md
+4-6Lines changed: 4 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -257,6 +257,10 @@ To have your custom pagination class be used by default, use the `DEFAULT_PAGINA
257
257
258
258
API responses for list endpoints will now include a `Link` header, instead of including the pagination links as part of the body of the response, for example:
259
259
260
+
![Link Header][link-header]
261
+
262
+
*A custom pagination style, using the 'Link' header'*
263
+
260
264
## Pagination & schemas
261
265
262
266
You can also make the pagination controls available to the schema autogeneration
@@ -268,12 +272,6 @@ The method should return a list of `coreapi.Field` instances.
268
272
269
273
---
270
274
271
-
![Link Header][link-header]
272
-
273
-
*A custom pagination style, using the 'Link' header'*
274
-
275
-
---
276
-
277
275
# HTML pagination controls
278
276
279
277
By default using the pagination classes will cause HTML pagination controls to be displayed in the browsable API. There are two built-in display styles. The `PageNumberPagination` and `LimitOffsetPagination` classes display a list of page numbers with previous and next controls. The `CursorPagination` class displays a simpler style that only displays a previous and next control.
0 commit comments