support django 2.1+ test client json data automatically serialized#6511
Conversation
auvipy
left a comment
There was a problem hiding this comment.
to have a better review need to add a test for the proposed change.
4607f28 to
4ed1e0e
Compare
|
@rpkilby updated with a test |
d368885 to
0a99e02
Compare
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
0a99e02 to
9ee6d46
Compare
|
Updated to |
9ee6d46 to
09fafd2
Compare
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
09fafd2 to
d28724e
Compare
|
bumped, I think the failed test was unrelated but this re-run the test suite |
auvipy
left a comment
There was a problem hiding this comment.
also, please rebase, and I think we might get rid of some checks to eleminate older version check
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
d28724e to
d579cc1
Compare
|
The failing test should be fixed by #9129 |
d579cc1 to
803e089
Compare
It's mentioned here https://docs.djangoproject.com/en/4.2/topics/testing/tools/#django.test.Client.post (specifically), and it's mentioned in the 2.1 release notes https://docs.djangoproject.com/en/4.2/releases/2.1/#tests (point 2) I'm not sure if you're asking for this to be included in the source, since there's not specifically a good place to put it (maybe the tests?), or if you're just asking for the release notes. |
|
@auvipy friendly ping, I can rebase, but wondering about ^^^ |
auvipy
left a comment
There was a problem hiding this comment.
looks good to me. should we also mention this in DRF docs?
|
Sure, I'll rebase and mention it. One thing that I realized with this request factory, when testing something yesterday, is that it returns a Django not a DRF request. This means that trying to access the I will look at the code, but would it be acceptable to return a DRF request instead? It proxies the native request so it's not a breaking change. I will look at the code, but from memory I think I can actually initialize it in way that would make sense. I will also look at the test client to make sure it does not rely on the factory or that if it does it works correctly. |
803e089 to
4579eae
Compare
|
I've left out changing the return type to |
|
Thanks, will review it again soon |
Description
_encode_datais alwaysTuple[bytes, str]rather thanTuple[Union[bytes,str], str]