I agree. If anything, I've always had issues with GET & POST
being different entities in the first place, but never with their
names. I would really like to see an entity combining both of
them. THAT one, maybe the preferred way of doing so, would be
lowercase, but RAW representations of incoming data, I for one
like them being upper case. Always makes me think twice before
playing with them.
The content negotiation thingy is also something I would like to
see more time invested in: I have a project where I have to hack
& slash DRF's implementation in order to get what I want, but
perhaps I'm tackling the issue incorrectly. But that's beside the
point. People will always try to do stuff framework developers
didn't think of. What's important is to give them a platform where
they can do so easily.
LP,
Jure
--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/bc60e809-6390-44fc-a07a-ed6e0f9eef86%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAMyDDM3%2BUucViDezhkWrFsk6ZsKViWjOgtA5aBm9pnzozdc%2Beg%40mail.gmail.com.
To unsubscribe from this group and stop receiving emails from it, send an email to django-d...@googlegroups.com.
I always took the capitalisation of GET &co to come from HTTP — I'd say that's where PHP took it from too but 🤷♀️
Hmmm. I have to say I think there are areas where we could get a better ROI on our time than this.
please do not use request.form_data as that is also misleading as you can POST many more sources than form data such as with APIs. post_data would be much clearer.
To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/b23d3b4a-9ff4-42ed-a08b-594f185b8d3b%40googlegroups.com.
Mr Steven Mapes Software Development and Solutions | |
This E-Mail and its contents are confidential, protected by law and legally privileged. Only access by the addressee is authorised. Any liability (in negligence, contract or otherwise) arising from any third party taking any action or refraining from taking any action on the basis of any of the information contained in this E-Mail is hereby excluded to the fullest extent of the law. In the event that you are not the addressee, please notify the sender immediately. Do not discuss, disclose the contents to any person or store or copy the information in any medium or use it for any purpose whatsoever.
You received this message because you are subscribed to a topic in the Google Groups "Django developers (Contributions to Django itself)" group.To unsubscribe from this topic, visit https://groups.google.com/d/topic/django-developers/Kx8BfU-z4_E/unsubscribe.To unsubscribe from this group and all its topics, send an email to django-develop...@googlegroups.com.To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAMyDDM19Ay4oAf26QaA8EyixrzDXHpXmFgtWijVf_%3D30W-gVBA%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/137322AE-3BF9-4B5F-B80D-7AC7EF298A6C%40getmailspring.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAHoz%3DMZgb-6o0-BMoYHrjwnF6YGBBcFO8A%3DBDSRJFvNi%2BL1eWw%40mail.gmail.com.
--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAMyDDM3%2BUucViDezhkWrFsk6ZsKViWjOgtA5aBm9pnzozdc%2Beg%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CABD5YeEFsbneB%3DfPKpE90cNukOUAKZejfp4Yo1N712mkmNVQHQ%40mail.gmail.com.
+1 request.dataWe shouldn’t be POSTists, there is also PUT and PATCH.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAM2o%3DwPf%2B_p2vh%3Ds9C_O03jebgQ%2Bd%2Be9oODnLoJ_HdM58HSJqg%40mail.gmail.com.
Would just like to point out - that's not the proposal. The proposal is to rename the existing request.POST to request.form_data, which is based on parsing application/x-www-form-urlencoded data from request.body. Browsers only send such data in the body on POST.
+1 request.dataWe shouldn’t be POSTists, there is also PUT and PATCH.Would just like to point out - that's not the proposal. The proposal is to rename the existing request.POST to request.form_data, which is based on parsing application/x-www-form-urlencoded data from request.body. Browsers only send such data in the body on POST.
On 7 May 2020, at 22:03, Florian Apolloner <f.apo...@gmail.com> wrote:forms with method="GET" are legitimate and wouldn't end up in `form_data` forms with method="GET" are legitimate and wouldn't end up in `form_data` which is imo quite confusing. Do we have any other options?
--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/66AB2042-8344-436B-A86A-2B9060BFAA17%40gmail.com.
--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAMyDDM3%2BUucViDezhkWrFsk6ZsKViWjOgtA5aBm9pnzozdc%2Beg%40mail.gmail.com.
- Users who don't know that GET queries mustn't have side effects and who don't want to bother will have an incentive to use a POST query to get the data in form_data; this is the safe option with regards to CSRF;
--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/5022af59-4280-4dca-a33e-d7ec79bc131b%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAMGFDKQwPiaS2UtCnaTQ-Q0HL7ZAP1iQyWDraECEiDKgj1gnsA%40mail.gmail.com.