Comparing version 1.1.0 to 1.1.1
{ | ||
"name": "apac", | ||
"description": "Amazon Product Advertising API Client for Node", | ||
"version": "1.1.0", | ||
"version": "1.1.1", | ||
"author": "Dustin McQuay <dmcquay@gmail.com>", | ||
@@ -6,0 +6,0 @@ "scripts": { |
@@ -5,12 +5,25 @@ [![Build Status](https://travis-ci.org/dmcquay/node-apac.svg?branch=master)](https://travis-ci.org/dmcquay/node-apac) | ||
apac (Amazon Product Advertising Client) will allow you to access the Amazon Product Advertising API from Node.js. It supports the newly required Request Signatures which can be a bit tedious to generate on your own. [Learn more about the Amazon Product Advertising API](https://affiliate-program.amazon.com/gp/advertising/api/detail/main.html). | ||
apac (Amazon Product Advertising Client) will allow you to access the Amazon Product Advertising API from Node.js. It | ||
supports the newly required Request Signatures which can be a bit tedious to generate on your own. | ||
[Learn more about the Amazon Product Advertising API](https://affiliate-program.amazon.com/gp/advertising/api/detail/main.html). | ||
node-apac is just a thin wrapper around Amazon's API. The only intent is to take care of request signatures, performing the HTTP requests, processing the responses and parsing the XML. You should be able to run any operation because the operation and all parameters are passed directly to the execute method just as they will be passed to Amazon. The result is that you feel like you're working directly with the API, but you don't have to worry about some of the more tedious tasks. | ||
node-apac is just a thin wrapper around Amazon's API. The only intent is to take care of request signatures, performing | ||
the HTTP requests, processing the responses and parsing the XML. You should be able to run any operation because the | ||
operation and all parameters are passed directly to the execute method just as they will be passed to Amazon. The result | ||
is that you feel like you're working directly with the API, but you don't have to worry about some of the more tedious | ||
tasks. | ||
## Changelog | ||
**v1.0.0** | ||
Errors are now returned as the first parameter of the callback function, instead of being processed by a separate OnError function. | ||
Note: This will break backwards compatibility with previous implementations where errors are processed by a separate function. Because of this, **version 1.0.0 will not be uploaded to NPM yet**, until more core features are added. Those who would like the new error processing implementation can get the module by cloning GitHub. | ||
Update: Very soon we will publish 1.0 with this change. If you still need the old OnError function, you'll need to grab an old version from git. | ||
**v1.1.0** | ||
- OperationHelper.execute now supports promises | ||
- Internal improvements such as more robust testing | ||
**v1.0.0** | ||
- Errors are now returned as the first parameter of the callback function, instead of being processed by a separate | ||
OnError function. Note: This breaks backwards compatibility with previous versions where errors are processed by a | ||
separate function. If you still need the old OnError function, you'll need to grab an old version from git. | ||
## Installation | ||
@@ -20,8 +33,5 @@ | ||
```bash | ||
$ npm install apac@latest | ||
$ npm install apac | ||
``` | ||
If you try to install without "@latest", it will try to install the most recent stable | ||
version, but there is no stable version yet. So for now you must specify latest. | ||
## Quick Start | ||
@@ -77,4 +87,4 @@ | ||
Both error 1 and 2 are returned in the promise catch callback, and error 3 would be in "results" as you successfully received a response from Amazon. | ||
(Note: old callback interface is still supported. See examples/example-item-search.js.) | ||
Both error 1 and 2 are returned in the promise catch callback, and error 3 would be in "results" as you successfully | ||
received a response from Amazon. (Note: old callback interface is still supported. See examples/example-item-search.js.) | ||
@@ -81,0 +91,0 @@ ## Obtaining credentials |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Major refactor
Supply chain riskPackage has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.
Found 1 instance in 1 package
145
2
32828