You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was making some request calls to the 'search' endpoint to get some information about paintings, and noticed some very odd behavior regarding the hasImages field. When encoding data via the requests library, the upper case 'T' in 'True' causes issues with the case sensitive nature of the hasImages field. You can see here that there is quite a large difference between manually encoding data and letting the library encode that data for you
I had tried using a string in my params (passing "true"), but that returned 0 results, so however this boolean is interpreted on the backend query behaves strange across languages.
The text was updated successfully, but these errors were encountered:
@HStep20 It is because in the first query the param q is set to %22%22 as a string while in the second the q is set to an emptystring and thus will be encoded to `` (nothing). The resultant urls are
I was making some request calls to the 'search' endpoint to get some information about paintings, and noticed some very odd behavior regarding the
hasImages
field. When encoding data via the requests library, the upper case 'T' in 'True' causes issues with the case sensitive nature of thehasImages
field. You can see here that there is quite a large difference between manually encoding data and letting the library encode that data for youManual Encoding (12111 results):
Requests Library Encoding (228 results):
I had tried using a string in my params (passing
"true"
), but that returned 0 results, so however this boolean is interpreted on the backend query behaves strange across languages.The text was updated successfully, but these errors were encountered: