* Updated types generation script
* Refactored api method definitions
* Updated test
- Removed old test code
- Added tsd dev dependency
- Rewritten test with tsd
* Removed unused dependencies
* Fixed definition
* Updated test
* Updated docs
* Improved events type definitions
* Updated test
* Minor fixes in the type definitons
* More type test
* Improved Transport type definitions
* Updated test
* Addressed comments
* Code generation
* Use RequestBody, Response and Context everywhere, also default Context to unknown
* Updated test
* body -> hasBody
* Fixed conflicts
* Updated code generation
* Improved request body type definition
* Updated code generation
* Use BodyType for both request and reponses generics
- Use extends for defining the RequestBody generic to force the user
following the same shape.
- BodyType and NDBodyType now accepts a generics to allow injecting
more specific types in the future
* API generation
* Updated test
* Updated docs
* Use BodyType also in ReponseError
* Removed useless client generics
* Renamed generics and types
- prefixed all generics with a T
- BodyType => RequestBody
- NDBodyType => RequestNDBody
- Added ResponseBody
* Updated test
* Updated docs
* Test ResponseBody as well
* Simplify overloads
* API generation
* Updated test
* Updated error types
With this pr we introduce the `client.child` API, which returns a new client instance that shares the connection pool with the parent client.
This feature can be handy if you need to have multiple client instances with different configurations, but with a shared connection pool.
Example:
```js
const { Client } = require('@elastic/elasticsearch')
const client = new Client({ node: 'http://localhost:9200' })
const child = client.child({
headers: { 'x-foo': 'bar' },
requestTimeout: 1000
})
client.info(console.log)
child.info(console.log)
```
**Open questions:**
* Currently, the event emitter is shared between the parent and the child(ren), is it ok?
* Currently, if you extend the parent client, the child client will have the same extensions, while if the child client adds an extension, the parent client will not be extended. Is it ok?
**Caveats:**
* You can override _any_ option except for the connection pool specific options (`ssl`, `agent`, `pingTimeout`, `Connection`, and `resurrectStrategy`).
* You can't specify a new `Connection` class.
* If you call `close` in any of the parent/child clients, every client will be closed.
_Note: the `nodeFilter` and `nodeSelector` options are now `Transport` options and no longer `ConnectionPool` options._
