Set the action on a view when override_method regardless of its None-ness

[cancan101]

No description provided.

[tomchristie]

Seems okay. Could you summarize the intent here, as #2062 is a pretty long thread. In what situation does your example get_serializer_class method (which is a pattern I'd advocate for) fail if we don't make this change?

[cancan101]

The way the browsable API resolves the form to render is by using override_method the incoming request and changes the method to POST it then takes that requests and calls get_serializer_class on the view. The problem is for a given action if the view has POST support but not get support the override_method leaves the action passed to get_serializer_class as None.

This means that in the special case where the originally resolved action on the GET request was None the get_serializer_class doesn't see what would have been the resolved action when/if the POST request comes in,

[tomchristie]

Probably time for this to go in.

Is there any point in writing a test case for this, or do we consider that overkill, given that it's prob a bit awkward to test for?

Don't think I particularly care either way but happy enough for anyone else to chime in.

[cancan101]

Thoughts?

[tomchristie]

Thoughts?

Merged! 😄