Fix #1621: Do not crash when encountering unexpected data in the request

[matthiask]

No description provided.

[tim-schilling]

Since the wrapping call already has this associated with the attribute on the request (get, post, files), I don't think we need to use the source. I think using an empty string or something constant will be more appropriate.

[matthiask]

Thanks, that's a good point. I have pushed an update but I haven't tested the update (yet)

[matthiask]

Here's how this could look. I broke get_sorted_request_variable on purpose to show cookies and query parameters as a raw block instead of as a table for the screenshot, but the code should still behave the same except if encountering some malformed data in request variables.

[matthiask]

@FinnGu I'd appreciate your input and/or testing if you have a way to do this.

[FinnGu]

@FinnGu I'd appreciate your input and/or testing if you have a way to do this.

Alright, setting up some tests on my end. And thank you for your quick PR!

[FinnGu]

@matthiask I just recently started using the DDT, so I don't know about all of its features. But for my use case, everything works flawlessly! I am now able to raise ParseErrors, ValidationErrors and basically all other exceptions that I am used to, without the DDT interfering with DRF ❤️

[matthiask]

Thanks! Good to hear.