Oliver Sauder

@jokiefer Wanted to follow up whether you are still interested in working on this PR?

I had some time at hand and wanted to make sure that this PR lands in the next version (which is hopefully released soon, waiting for DRF to release a...

This is a fairly old issue and there might be some confusion. So to clarify the specification states that the include query param are relationship field names and not resource...

Could [SerializerMethodResourceRelatedField](https://github.com/django-json-api/django-rest-framework-json-api/blob/c392793b68dd1783cd20a2652f90fdfef638b4e6/example/serializers.py#L124) be what you are looking for? Otherwise in the same file linked above there are many other examples.

I am not 100% certain but when looking at the code it should work without passing on a model. However I am not sure why you do not want to...

No this is currently not possible. I had a quick look at the renderer and I do not see a quick workaround either to override the url of a relationship...

I unfortunately do not have access to a GitLab instance anymore where this issue occurred. @bluespider42 can you still reproduce this issue?

@avacaru No this issue is specifically about accessing request.data in get_serializer_class. Your issue is actually related to #1140 and when implemented as mentioned in https://github.com/django-json-api/django-rest-framework-json-api/issues/1140#issuecomment-1483270751 your issue should be fixed...

No, this has not been implemented yet. To implement it, I would suggest that a `get_meta(rself, esource)` returning a dict is added to `ResourceRelatedField` and then called at the appropriate...

@avacaru Thanks for the additional info. The issue might not just be with the include param as initially reported here, but also the example you provided. I have an idea,...