Context Navigation

Changes between Version 1 and Version 2 of Ticket #32362, comment 2

v1	v2
3	3	This is essentially a duplicate of #21442, plus see also #32646, #32259, as well as [https://forum.djangoproject.com/t/technical-board-vote-on-ticket-32259-modernize-request-attribute-names/10255 this discussion on the Django Forum], and experiments such as [https://github.com/kezabelle/django-formality kezabelle/django-formality].
4	4
5		There's plenty of groundwork going on... — one of the first steps would be to tease-out [https://github.com/django/django/blob/89e695a69b16b8c0e720169b3ca4852cfd0c485f/django/http/request.py#L350 the request body parsing from `_load_post_and_files()`] so that we might add a `request.data` property that was able to handle (by default) b~~y JSON and form-encoded data, plus multipart~~. I think if we can make progress there, we wouldn't be too far off. (Parts such as JSONResponse are already in place — you can do this already, but it's still a little manual…)
	5	There's plenty of groundwork going on... — one of the first steps would be to tease-out [https://github.com/django/django/blob/89e695a69b16b8c0e720169b3ca4852cfd0c485f/django/http/request.py#L350 the request body parsing from `_load_post_and_files()`] so that we might add a `request.data` property that was able to handle (by default) both JSON and form-encoded data, plus multipart variants. I think if we can make progress there, we wouldn't be too far off. (Parts such as JSONResponse are already in place — you can do this already, but it's still a little manual…)