apollo-link-batch-http
Advanced tools
Comparing version 1.2.12 to 1.2.13
{ | ||
"name": "apollo-link-batch-http", | ||
"version": "1.2.12", | ||
"version": "1.2.13", | ||
"description": "Batch HTTP transport layer for GraphQL", | ||
@@ -37,5 +37,5 @@ "author": "Evans Hauser <evanshauser@gmail.com>", | ||
"dependencies": { | ||
"apollo-link": "^1.2.12", | ||
"apollo-link-batch": "^1.1.13", | ||
"apollo-link-http-common": "^0.2.14", | ||
"apollo-link": "^1.2.13", | ||
"apollo-link-batch": "^1.1.14", | ||
"apollo-link-http-common": "^0.2.15", | ||
"tslib": "^1.9.3" | ||
@@ -47,12 +47,12 @@ }, | ||
"devDependencies": { | ||
"@types/graphql": "14.2.0", | ||
"@types/jest": "24.0.14", | ||
"@types/graphql": "14.2.3", | ||
"@types/jest": "24.0.18", | ||
"fetch-mock": "6.5.2", | ||
"graphql": "14.3.1", | ||
"graphql": "14.5.4", | ||
"graphql-tag": "2.10.1", | ||
"jest": "24.8.0", | ||
"jest": "24.9.0", | ||
"object-to-querystring": "1.0.8", | ||
"proxyquire": "1.8.0", | ||
"rimraf": "2.6.3", | ||
"rollup": "1.15.4", | ||
"rimraf": "2.7.1", | ||
"rollup": "1.20.3", | ||
"ts-jest": "22.4.6", | ||
@@ -79,3 +79,3 @@ "tslint": "5.17.0", | ||
}, | ||
"gitHead": "f902ab977d7d173951528a0bc2e38521b2afc096" | ||
"gitHead": "74d412528dd474fc41ee0bf504e36e01d7e05e2b" | ||
} |
@@ -16,3 +16,3 @@ --- | ||
<h2 id="options">Options</h2> | ||
## Options | ||
@@ -22,3 +22,3 @@ The batch http link accepts an object with some options to customize the behavior | ||
http options follow the same structure as the | ||
[apollo-link-http](http.html#options): | ||
[apollo-link-http](http#options): | ||
@@ -46,7 +46,7 @@ * `uri`: the URI key is a string endpoint -- will default to "/graphql" if not | ||
<h2 id="fetch">Fetch polyfill</h2> | ||
## Fetch polyfill | ||
The batch http link relies on having `fetch` present in your runtime environment. If you are running on react-native, or modern browsers, this should be no problem. If you are targeting an environment without `fetch` such as older browsers or the server, you will need to pass your own `fetch` to the link through the options. We recommend [`unfetch`](https://github.com/developit/unfetch) for older browsers and [`node-fetch`](https://github.com/bitinn/node-fetch) for running in Node. | ||
<h2 id="context">Context</h2> | ||
## Context | ||
@@ -69,3 +69,3 @@ The Batch Http Link currently uses the context in two different ways, per batch | ||
<h3 id="persisted-queries">Persisted queries</h3> | ||
### Persisted queries | ||
@@ -90,11 +90,11 @@ The batch http link supports an advanced GraphQL feature called persisted queries. This allows you to not send the stringified query over the wire, but instead send some kind of identifier of the query. To support this you need to attach the id somewhere to the extensions field and pass the following options to the context: | ||
<h2 id="error">Errors</h2> | ||
## Errors | ||
The batch http link handles errors on a per batch basis with the same semantics found in [apollo-link-http](http.html#error): | ||
The batch http link handles errors on a per batch basis with the same semantics found in [apollo-link-http](http#errors). | ||
<h2 id="custom">Custom fetching</h2> | ||
## Custom fetching | ||
You can use the `fetch` option when creating an http-link to do a lot of custom networking. This is useful if you want to modify the request based on the calculated headers or calculate the uri based on the operation: | ||
<h3 id="custom-auth">Custom auth</h3> | ||
### Custom auth | ||
@@ -115,3 +115,3 @@ ```js | ||
<h3 id="dynamic-uri">Dynamic URI</h3> | ||
### Dynamic URI | ||
@@ -118,0 +118,0 @@ ```js |
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
69684
Updatedapollo-link@^1.2.13
Updatedapollo-link-batch@^1.1.14