tumblr.apiFetch does not correctly interpret queryParams as supplied by API response about docs HOT 3 CLOSED

Yep, looks good; thanks!

from docs.

The apiFetch() queryParams documentation states "This will encode the params and append them to the request URL, so you don't need to do that yourself", but this is evidently not true when using API response queryParams, as any object-type value is not converted to an acceptable format and is instead directly converted to string - completely discarding any data within.

Looks like you found a bug with this! We're taking a look internally and we'll either fix this up so it does work as expected (and as indicated in the docs) or we'll update the docs with the best path forward here. Thank you!

from docs.

@AprilSylph this should hopefully be fixed now - mind checking to confirm that what we updated is what you noticed and expected?

from docs.