I agree with Adam that it should be deprecated with no replacement.
The content negotiation is something that should be in but not as a
replacement of it, as a general improvement.
I think there shouldn't be a replacement because "is_ajax" asks whether it
came from a ""regular"" browser instead o
What I meant by that is it’s not an approach that scales well to lots of views.
It might be better to have separate endpoints to return JSON (e.g adding a
/json suffix), and in the past this has made services I’ve worked on a lot more
maintainable and easy to understand. But it’s not as quick to
“In my opinion there are not many good reasons to have to change behaviour if a
request is made via XHR. I think the most common usage is to have a single view
that returns a JSON response or a HTML response depending on if XHR is used
(https://github.com/search?l=Python&q=request.is_ajax&type=C
We've made the final (hopefully) release on the way to Django's next
major release, Django 3.0! Check out the blog post:
https://www.djangoproject.com/weblog/2019/nov/18/django-30-release-candidate-1-released/
--
You received this message because you are subscribed to the Google Groups "Django
