Currently, fetch deserialises the JSON to check for errors, even if the user wants the raw result. This could be a performance issue. Furthermore, the requests.Response object does not cache its .json() result, so when the user doesn't want the raw result, they deserialise the same (possibly large) JSON twice.
Should raw automatically apply no_verify? Is there even a need to have two separate switches?
Currently,
fetch
deserialises the JSON to check for errors, even if the user wants theraw
result. This could be a performance issue. Furthermore, therequests.Response
object does not cache its.json()
result, so when the user doesn't want theraw
result, they deserialise the same (possibly large) JSON twice.Should
raw
automatically applyno_verify
? Is there even a need to have two separate switches?