Path to view on error or warning

[HansAarneLiblik]

Not a bug, but rather a feature-request

When generating the schema and there are errors for some views, it is difficult to track down the view as there may be views with same name in multiple apps

Error #0: task_list: unable to guess serializer. ...

It would be really great, if the path to the view was also printed out, e.g. url from self.path or somehow the full filepath myapp/views.py

Error #0: task_list: unable to guess serializer. ... Ignoring view for now (myapp/app1/views.py)
...
Error #12: task_list: unable to guess serializer. ... Ignoring view for now (myapp/app4/views.py)

[HansAarneLiblik]

For me, covering just these 3 cases is enough (I edited your source locally for testing)

https://github.com/tfranzel/drf-spectacular/blob/master/drf_spectacular/openapi.py#L870
https://github.com/tfranzel/drf-spectacular/blob/master/drf_spectacular/openapi.py#L1075
https://github.com/tfranzel/drf-spectacular/blob/master/drf_spectacular/openapi.py#L1133

[tfranzel]

Hey @HansAarneLiblik, that is an interesting suggestion. Certainly useful for people migrating and having lots of warnings.

The meat of the matter lies here:

drf-spectacular/drf_spectacular/drainage.py

Line 83 in 2aabb8b

def add_trace_message(trace_message):

drf-spectacular/drf_spectacular/contrib/django_filters.py

Line 60 in 2aabb8b

with add_trace_message(filterset_class.__name__):

drf-spectacular/drf_spectacular/generators.py

Line 238 in 2aabb8b

with add_trace_message(getattr(view, '__class__', view).__name__):

I'm open to suggestions on how to make this work.

[HansAarneLiblik]

I created a PR #868

Don't really know how I feel about the duplication of _TRACES logic though