Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OrderingFilter should call get_serializer_class() to determine default fields. #3957

Closed
5 of 6 tasks
bmampaey opened this issue Feb 22, 2016 · 2 comments
Closed
5 of 6 tasks

Comments

@bmampaey
Copy link

Checklist

  • I have verified that that issue exists against the master branch of Django REST framework.
  • I have searched for similar issues in both open and closed tickets and cannot find a duplicate.
  • This is not a usage question. (Those should be directed to the discussion group instead.)
  • This cannot be dealt with as a third party library. (We prefer new functionality to be in the form of third party libraries where possible.)
  • I have reduced the issue to the simplest possible case.
  • I have included a failing test as a pull request. (If you are unable to do so we can still accept the issue.)

GenericAPIView says

You'll need to either set these attributes,
or override get_queryset()/get_serializer_class().

But in the method get_valid_fields of the OrderingFilter class, it gets the serializer_class like so

serializer_class = getattr(view, 'serializer_class')

I believe it should be

serializer_class = view.get_serializer_class()

Benjamin

@tomchristie
Copy link
Member

Thanks for the well written issue 👍

@jpadilla
Copy link
Member

Oh yeah, this is an actionable ticket! 👏 @bmampaey want to put a a PR together to address this?

@tomchristie tomchristie changed the title OrderingFilter gets directly the serializer_class from the view instead of calling get_serializer_class() OrderingFilter should call get_serializer_class() to determine default fields. Jun 1, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants