Freakish whitespace in SP-API JSON responses #535
Comments
|
This is a very old issue that is probably not getting as much attention as it deserves. We encourage you to check if this is still an issue after the latest release and if you find that this is still a problem, please feel free to open a new issue and make a reference to this one. |
|
Can confirm this is still broken. |
|
This is a very old issue that is probably not getting as much attention as it deserves. We encourage you to check if this is still an issue after the latest release and if you find that this is still a problem, please feel free to open a new issue and make a reference to this one. |
|
This should not be closed. It could be converted to a "discussion" since that's apparently where bug reports go now. |
|
This is a very old issue that is probably not getting as much attention as it deserves. We encourage you to check if this is still an issue after the latest release and if you find that this is still a problem, please feel free to open a new issue and make a reference to this one. |
|
Still broken. |
|
This is a very old issue that is probably not getting as much attention as it deserves. We encourage you to check if this is still an issue after the latest release and if you find that this is still a problem, please feel free to open a new issue and make a reference to this one. |
|
Still broken. |
|
This is a very old issue that is probably not getting as much attention as it deserves. We encourage you to check if this is still an issue after the latest release and if you find that this is still a problem, please feel free to open a new issue and make a reference to this one. |
|
Still broken. |
|
Can you provide a submission ID and endpoint you are calling of where you are getting these whitespaces in your response? Weiling Gu |
|
I'm pretty sure every SP-API call has this problem. |
|
Hi @johnkw, Thank you for bringing this issue to our attention. We submitted the feature request to remove whitespaces for review. Once we receive additional information we will post an update. Thanks |
|
@johnkw Can you provide request ID for each endpoint you are getting white space issue? Weiling |
|
/batches/products/pricing/v0/itemOffers x-amzn-RequestId: 71ad84ad-be1a-4a1f-aa42-910ef1e7de2e |
|
@johnkw Can you provide timestamp and region as well? |
|
How do I determine what the "region" is? |
|
Date: Thu, 10 Oct 2024 18:51:37 GMT Date: Thu, 10 Oct 2024 18:51:02 GMT |
|
@johnkw Thanks for sharing. What is your marketplace? |
|
'MarketplaceId': 'ATVPDKIKX0DER' |
|
This issue is scheduled to close soon. If you are still encountering problems, please feel free to open a new issue and make a reference to this one. |
|
This has not been fixed. By the way, I never mentioned it, but ideally there should be no whitespace at all for efficiency's sake. |
|
This issue is scheduled to close soon. If you are still encountering problems, please feel free to open a new issue and make a reference to this one. |
|
While this issue is not terribly important, it would be good to leave it open until it's actually fixed. |
|
This issue is scheduled to close soon. If you are still encountering problems, please feel free to open a new issue and make a reference to this one. |
|
While this issue is not terribly important, it would be good to leave it open until it's actually fixed. |
This has bothered me for years but I held back on filing a bug report. This affects most (or all?) API responses. But just for example here's the response from testing bug #370:
b'\n{\n\n\t\n\t\t\t\t\t\t"payload": {\n\t\t\t\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t"ShipmentData":\n\t\t\t\t[\n\t\t\t\t\t\t\t\t]\n\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t}\n\t\t\t}\n\n'
It's hilarious how it alternates back and forth between linefeeds and tabs, without ever outputting actual data.
This may not violate any JSON protocol, but it makes debug logs difficult to read for no reason.
The text was updated successfully, but these errors were encountered: