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
{{ message }}
This repository has been archived by the owner on Jul 4, 2021. It is now read-only.
The way the query params are build for sorting purposes doesn't play nice with the default filtering solution from Django Rest Framework.
Backbone Paginator is using two parameters to describe the filtering, where DRF is using only one, in which he's expecting a list of fields in the form ordering='column' or ordering='-column' for ascending, respectively descending sorting.
Would it be possible to move the params building code out in an overridable function ? at the moment, it resides in the fetch function, forcing me to override the whole function.
The text was updated successfully, but these errors were encountered:
The way the query params are build for sorting purposes doesn't play nice with the default filtering solution from Django Rest Framework.
Backbone Paginator is using two parameters to describe the filtering, where DRF is using only one, in which he's expecting a list of fields in the form ordering='column' or ordering='-column' for ascending, respectively descending sorting.
Would it be possible to move the params building code out in an overridable function ? at the moment, it resides in the fetch function, forcing me to override the whole function.
The text was updated successfully, but these errors were encountered: