Why does Wing complain about objects.all() in my views? It runs perfectly otherwise. I'm not sure why anyone else has not posed the question either, as far as I can tell. Is there something I'm missing?
+1 if we could find a way to hint Wing that "any instance of subclass of django.models.Model contains the following methods: objects, DoesNotExist, MultipleObjectsReturned"....
This is due to how Django classes are implemented. The warnings can be disabled by clicking on the red X beside the warning in the warning list or in the tooltip displayed for the warning.
We plan to improve this in future releases.
Hi, Is this also true of:-
response.status_code
and
.DoesNotExist
which also displays the same attribute undefined warning...?
Dave
It's probably also true in these cases. In general, if the attributes are valid when you run or debug the warnings are spurious and should be disabled.
Comments