Silent failing of the fields definition

[Berthier Lemieux]

Hi,
   I noticed that if the definition of the fields of a serializer is erroneous (most commonly because of a typo), the DRF swallows the error and later call to is_valid() will always return true.
 
   Errors like these:
  

class ImageSerializer(serializers.ModelSerializer):
    class Meta:
        model = Feedback
        fields = ('file') #Oops, this is not a tuple, but a string. It should be ('file',)

 
   Since the error is caught down below and not visible to the user of the serializer, figuring out what's going wrong is not trivial for someone not familiar with the inner workings of the framework. The framework would be (slightly) easier to use if the error would be visible. Would it be possible to add some debug trace or make sure the error is thrown when the bogus serializer is imported?

-Berthier

[Xavier Ordoquy]

Unfortunately this is hard to catch mostly because strings themselves are iterables.

Regards,

Xavier,

Linovia.