query_params in favor of QUERY_PARAMS

This commit is contained in:
José Padilla 2015-03-29 17:04:23 -04:00
parent ba951f3339
commit 911da8a2b9
2 changed files with 3 additions and 3 deletions

View File

@ -72,7 +72,7 @@ We can override `.get_queryset()` to deal with URLs such as `http://example.com/
by filtering against a `username` query parameter in the URL. by filtering against a `username` query parameter in the URL.
""" """
queryset = Purchase.objects.all() queryset = Purchase.objects.all()
username = self.request.QUERY_PARAMS.get('username', None) username = self.request.query_params.get('username', None)
if username is not None: if username is not None:
queryset = queryset.filter(purchaser__username=username) queryset = queryset.filter(purchaser__username=username)
return queryset return queryset

View File

@ -133,9 +133,9 @@ May be overridden to provide more complex behavior with filters, such as using d
For example: For example:
def get_filter_backends(self): def get_filter_backends(self):
if "geo_route" in self.request.QUERY_PARAMS: if "geo_route" in self.request.query_params:
return (GeoRouteFilter, CategoryFilter) return (GeoRouteFilter, CategoryFilter)
elif "geo_point" in self.request.QUERY_PARAMS: elif "geo_point" in self.request.query_params:
return (GeoPointFilter, CategoryFilter) return (GeoPointFilter, CategoryFilter)
return (CategoryFilter,) return (CategoryFilter,)