Add support for class level prepare methods on arguments

[DougEdey]

Issue: #4715

I think this is what @eapache-opslevel was aluding to, it checks to see if the prepare method exists on the object or the owner (class method), and handles each approproiately

• For Object, don't send the context, it'll be there already
• For the Owner, send the context (like we do already for prepare blocks)
• If neither exist, give a clear error instead of a no method found error.

[eapache-opslevel]

This makes sense based on my understanding here. Left a few questions about the tests though.

[rmosolgo]

Hey, thanks for exploring this improvement!

I'm open to the proposed change, but I want to double-check my impression: could this cause problems for existing prepare: usages? I mean, if the configured prepare: method exists on a field's owner type (eg, a Field instance or an InputObject class), then the code will start choosing that method instead of the method on obj. Does that sound right to you?

If so, could the order of these conditions be reversed to avoid that possibility?

[DougEdey]

Good point @rmosolgo

If so, could the order of these conditions be reversed to avoid that possibility?

Yup, I've swapped the check order so we keep existing behaviour first!

[rmosolgo]

Thanks for this improvement!