Eric Blade
I was just playing with some reporting functionality, and I requested a list that apparently had 11 items, and was paginated by 0-9 and then 10.. the second page was...
Per #111 @pwrnrd mentioned >Btw, if your looking at reporting, what might be very nice to implement is this: https://docs.developer.amazonservices.com/en_US/notifications/Notifications_ReportProcessingFinishedNotification.html . it looks like we could implement a SQS queue...
esdoc had decent looking output, but is very opinionated -- it required a 3rd party plugin to work with require(), which is kind of ridiculous, and it treated everything as...
output from my app: ```` **** getReports params { region: 'US', [0] access_token: 'deleted', [0] amazonMerchantId: 'deleted', [0] amazonAuthToken: 'deleted', [0] reportId: '15174565821018052', [0] reportType: 'FeedSummaryReport' } [0] * getAmazonReport...
this is all i get along with a partial dump of a massive report that a user was attempting to download. ```` at MwsAdvanced.doRequest (Z:\www\random\pos\server\node_modules\mws-advanced\lib\index.js:140:25) [0] at processTicksAndRejections (internal/process/task_queues.js:86:5) ````
just received this on my service, a few times, i'm not sure if it's related to the new quota handling code, or if it's something inside my app service. ````...
example: GetReportList and GetReportListByNextToken share the same request quota. Lib does not currently understand that. Probably need to include a "throttle key" option in the throttle data that different calls...
Otherwise you have to hit the server just to get back a "Extraneous Whitespace" error. ```` \nSenderInvalidRequestparameter ASINList.ASIN.1 failed a validation check: Extraneous whitespace for input value: "142210284X "8a0f16d9-8a95-4935-be96-2a8f409e4685 ````
... i'm not 100% sure where I'm going with this thought -- it's probably safe to assume that Amazon will always send valid data, and even if they didn't, we'd...