@@ -135,7 +135,7 @@ simply don't use this filter backend.
135135#### OrderingFilter
136136
137137` OrderingFilter ` implements the [ JSON: API ` sort ` ] ( http://jsonapi.org/format/#fetching-sorting ) and uses
138- DRF's [ ordering filter] ( http ://django-rest-framework.readthedocs.io/en/latest /api-guide/filtering/#orderingfilter) .
138+ DRF's [ ordering filter] ( https ://www. django-rest-framework.org /api-guide/filtering/#orderingfilter) .
139139
140140Per the JSON: API specification, "If the server does not support sorting as specified in the query parameter ` sort ` ,
141141it ** MUST** return ` 400 Bad Request ` ." For example, for ` ?sort=abc,foo,def ` where ` foo ` is a valid
@@ -205,7 +205,7 @@ As this feature depends on `django-filter` you need to run
205205#### SearchFilter
206206
207207To comply with JSON: API query parameter naming standards, DRF's
208- [ SearchFilter] ( https://django-rest-framework.readthedocs.io/en/latest /api-guide/filtering/#searchfilter ) should
208+ [ SearchFilter] ( https://www. django-rest-framework.org /api-guide/filtering/#searchfilter ) should
209209be configured to use a ` filter[_something_] ` query parameter. This can be done by default by adding the
210210SearchFilter to ` REST_FRAMEWORK['DEFAULT_FILTER_BACKENDS'] ` and setting ` REST_FRAMEWORK['SEARCH_PARAM'] ` or
211211adding the ` .search_param ` attribute to a custom class derived from ` SearchFilter ` . If you do this and also
0 commit comments