Redirect on DELETE when using AdminRenderer

[jpadilla]

Checklist

• I have verified that that issue exists against the master branch of Django REST framework.
• I have searched for similar issues in both open and closed tickets and cannot find a duplicate.
• This is not a usage question. (Those should be directed to the discussion group instead.)
• This cannot be dealt with as a third party library. (We prefer new functionality to be in the form of third party libraries where possible.)
• I have reduced the issue to the simplest possible case.
• I have included a failing test as a pull request. (If you are unable to do so we can still accept the issue.)

Steps to reproduce

Following up on #4106 for an improvement

Expected behavior

Redirect back to /users/ after DELETE.

Actual behavior

URL is still set to /users/:id/

[rocktavious]

+1 I have experienced this, i got around it by hacking the ajaxform.js script that's used, but would love for a framework supported solution/fix.

[carltongibson]

This is related to something I was thinking about before the Kickstarter campaign (but haven't had time to ponder since)... — it would be nice if we could use a DRF backend to serve various versions of a site/API.

We can do that to an extent but sometimes (like here) you need a slightly different behaviour — based on the accepted renderer.

For pure JavaScript Apps you can serve a single page and then eat the JSON but there a regular HTML driven webpage needs something like Vanilla Views' form_valid hook — which can somehow proxy to the renderer — to specify the next — to use a term — behaviour.

(Obviously the renderer is a bad place for this kind of logic — but it's the sole thing that varies in line with the requirement here.)

I'd like to see something like this. I'm not sure it's simple.

[lovelydinosaur]

Resolved via #4106.

[jpadilla]

Yay!

[lovelydinosaur]

Thanks as ever, @jpadilla!

😄