* change logging to metrics and add section on Engine
* add to the migration guide
* address feedback and add clarity around logFunction
* address feedback for migration guide
* core: return response object from runHttpQuery
* core: change gqlResponse to graphqlResponse and add custom RequestInit type
* core: add cache-control headers based on the calcualted maxAge
* core: add extensions check during cache-control header creation
* core: create headers when cacheControl is not enabled otherwise pass through extensions
* express: initial tests of CDN cach-contol headers
* core: fixed tests with applyMiddleware and pass cacheControl config
* core: cache hint fixes, ignore when no maxAge, and check for rootKeys
* core: check for hints of length 0
* core: node 10 fails file upload test for some stream reason
* docs: add cdn caching section to features
* add space after // in comments
* fix feedback: proxy alignment and response creation
Adds cache-control toggles for http header calculation and stripping out
the cache control extensions from the respose.
Brings the default calculation of headers in line with the proxy.
* fix links in comments
* fix tests with null dereference
* update cdn docs and migration guide to include latest cdn configuration
* add not for engine migration to set engine to false
* add engine set to false in migration guide
* express: fixed tests
* address feedback to use omit and documentation
* docs: cdn caching is alternative to full response caching
* add back epipe check in upload tests
This Pull Request updates dependency `hexo-versioned-netlify-redirects` from `^1.0.7` to `v1.0.7`
---
This PR has been generated by [Renovate Bot](https://renovatebot.com).
This removes an unnecessary instruction to install `apollo-server` when using the middleware option with Apollo Server 2.0.
While this was necessary in earlier versions of the Apollo Server 2.0 alpha and beta releases, it is no longer needed.
In order to provide a more universal README.md across all documentation
deployment repositories, and most importantly, to reference the so-called
"documentation for the documentation".
This was still linked from the v2 getting started page. While it will
eventually link to the "Deployment" guide index page where we'll offer
guides for other deployment options, that content is not written.
For now, we'll offer those getting statred to deploy with Heroku, which is
written!
Ref: https://twitter.com/jevakallio/status/1007915638919192577
cc (and thanks) to @jevakallio for pointing this out.
