Adapt SerializerMethodResourceRelatedField behaviro to DRF SerializerMethodField

[David-Guillot]

Hi there,

DRF's SerializerMethodField makes it easy to avoid defining a method name as it auto-computes a method name by prepending get_ to the field source.

With DJA's SerializerMethodResourceRelatedField, one has to define the source attribute as without it, the method name conflicts with the field name (i'm not sure to be crystal-clear here 😕 ).

I find it:

• Annoying (in a very minor way)
• Not consistent with what developers are used to with vanilla DRF

So if you agree with me, i can probably open a PR that adds this bit of sugar (although i'm not sure to understand all the implications for the read/write use case, but i can give it a try).

So what do you think?

[sliverc]

I see your point and I think it would be great if SerializerMethodResourceRelatedField could be consistent with SerializerMethodField. It would be great if you could give it a try.

Such a change might be related to #632

[auvipy]

does this need to be worked yet?

[sliverc]

This hasn't been worked on yet and any help is appreciated.