Skip to content

Commit 372f4fd

Browse files
linchiwei123rpkilby
authored andcommitted
Update pagination.md (#6787)
it seems like that
1 parent eebc579 commit 372f4fd

File tree

1 file changed

+4
-6
lines changed

1 file changed

+4
-6
lines changed

docs/api-guide/pagination.md

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -257,6 +257,10 @@ To have your custom pagination class be used by default, use the `DEFAULT_PAGINA
257257

258258
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:
259259

260+
![Link Header][link-header]
261+
262+
*A custom pagination style, using the 'Link' header'*
263+
260264
## Pagination & schemas
261265

262266
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.
268272

269273
---
270274

271-
![Link Header][link-header]
272-
273-
*A custom pagination style, using the 'Link' header'*
274-
275-
---
276-
277275
# HTML pagination controls
278276

279277
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

Comments
 (0)