DynamicRelationField ignores queryset param

The code below always returns all the units associated with the curriculum being serialized, and ignores the filter.

class CurriculumSerializer(DynamicModelSerializer):
    units = DynamicRelationField('UnitSerializer', many=True, queryset=Unit.objects.filter(id=1))

    class Meta:
        model = Curriculum
        name = 'curriculum'
        fields = ('id', 'units')


class UnitSerializer(DynamicModelSerializer):
    class Meta:
        model = Unit
        name = 'unit'
        fields = ('id',)

When offloading the queryset to a function with an embedded print or ipdb, such as

def get_unit_queryset(field):
    print 'IS THIS EVER HAPPENING?"
    return Unit.objects.filter(id=1)

the result is the same and the print statement is never executed. The function is never called.

[TwunTee]

Most of the magic happens when using filter_queryset where it uses the DynamicFilterBackend. When you are using list_route or detail route I guess you wont be filtering with self.filter_queryset, queryset argument wont be called and you also lose out on the prefetch optimization etc. For anyone looking out for solution make a subclass of the DynamicFilterBackend and call filter_queryset which would set the serializer too else it would end up getting it from get_queryset method. I found it cleaner to use multiple model viewset for my use case and subclassing the backend to be really a messed up hack. If i come across a need for it later on or if i find time, will make a gist of it. If any one wants to write a solution meanwhile I can help out

[TwunTee]

@simkimsia Yes!