Commit c91229aa by Xavier Ordoquy

PAGINATE_BY_PARAM and MAX_PAGINATE_BY removed in 3.3

parent c90cf828
...@@ -133,31 +133,25 @@ The default page size to use for pagination. If set to `None`, pagination is di ...@@ -133,31 +133,25 @@ The default page size to use for pagination. If set to `None`, pagination is di
Default: `None` Default: `None`
#### MAX_PAGINATE_BY #### PAGINATE_BY_PARAM
--- ---
**This setting is pending deprecation.** **This setting has been removed.**
See the pagination documentation for further guidance on [setting the pagination style](pagination.md#modifying-the-pagination-style). See the pagination documentation for further guidance on [setting the pagination style](pagination.md#modifying-the-pagination-style).
--- ---
The maximum page size to allow when the page size is specified by the client. If set to `None`, then no maximum limit is applied. #### MAX_PAGINATE_BY
For example, given the following settings:
REST_FRAMEWORK = { ---
'PAGINATE_BY': 10,
'PAGINATE_BY_PARAM': 'page_size',
'MAX_PAGINATE_BY': 100
}
A client request like the following would return a paginated list of up to 100 items. **This setting is pending deprecation.**
GET http://example.com/api/accounts?page_size=999 See the pagination documentation for further guidance on [setting the pagination style](pagination.md#modifying-the-pagination-style).
Default: `None` ---
### SEARCH_PARAM ### SEARCH_PARAM
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment