* 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
189 lines
4.3 KiB
Plaintext
189 lines
4.3 KiB
Plaintext
[[typescript]]
|
|
== TypeScript support
|
|
|
|
The client offers a first-class support for TypeScript, since it ships the type
|
|
definitions for every exposed API.
|
|
|
|
NOTE: If you are using TypeScript you will be required to use _snake_case_ style
|
|
to define the API parameters instead of _camelCase_.
|
|
|
|
Other than the types for the surface API, the client offers the types for every
|
|
request method, via the `RequestParams`, if you need the types for a search
|
|
request for instance, you can access them via `RequestParams.Search`.
|
|
Every API that supports a body, accepts a
|
|
https://www.typescriptlang.org/docs/handbook/generics.html[generics] which
|
|
represents the type of the request body, if you don't configure anything, it
|
|
will default to `RequestBody`. +
|
|
`RequestBody`, along with `RequestNDBody` and `ResponseBody` are defined inside the client, and it looks like this:
|
|
[source,ts]
|
|
----
|
|
type RequestBody<T = Record<string, any>> = T | string | Buffer | ReadableStream
|
|
type RequestNDBody<T = Record<string, any>[]> = T | string[] | Buffer | ReadableStream
|
|
type ResponseBody<T = Record<string, any>> = T | string | boolean | ReadableStream
|
|
----
|
|
|
|
For example:
|
|
|
|
[source,ts]
|
|
----
|
|
import { RequestParams } from '@elastic/elasticsearch'
|
|
|
|
interface SearchBody {
|
|
query: {
|
|
match: { foo: string }
|
|
}
|
|
}
|
|
|
|
const searchParams: RequestParams.Search<SearchBody> = {
|
|
index: 'test',
|
|
body: {
|
|
query: {
|
|
match: { foo: 'bar' }
|
|
}
|
|
}
|
|
}
|
|
|
|
// This is valid as well
|
|
const searchParams: RequestParams.Search = {
|
|
index: 'test',
|
|
body: {
|
|
query: {
|
|
match: { foo: 'bar' }
|
|
}
|
|
}
|
|
}
|
|
----
|
|
|
|
You can find the type definiton of a response in `ApiResponse`, which accepts a
|
|
generics as well if you want to specify the body type, otherwise it defaults to
|
|
`BodyType`.
|
|
|
|
[source,ts]
|
|
----
|
|
interface SearchResponse<T> {
|
|
hits: {
|
|
hits: Array<{
|
|
_source: T;
|
|
}>
|
|
}
|
|
}
|
|
|
|
// Define the interface of the source object
|
|
interface Source {
|
|
foo: string
|
|
}
|
|
|
|
client.search(searchParams)
|
|
.then((response: ApiResponse<SearchResponse<Source>>) => console.log(response))
|
|
.catch((err: Error) => {})
|
|
----
|
|
|
|
=== A complete example
|
|
|
|
[source,ts]
|
|
----
|
|
import {
|
|
Client,
|
|
// Object that contains the type definitions of every API method
|
|
RequestParams,
|
|
// Interface of the generic API response
|
|
ApiResponse,
|
|
} from '@elastic/elasticsearch'
|
|
|
|
const client = new Client({ node: 'http://localhost:9200' })
|
|
|
|
// Define the type of the body for the Search request
|
|
interface SearchBody {
|
|
query: {
|
|
match: { foo: string }
|
|
}
|
|
}
|
|
|
|
// Complete definition of the Search response
|
|
interface ShardsResponse {
|
|
total: number;
|
|
successful: number;
|
|
failed: number;
|
|
skipped: number;
|
|
}
|
|
|
|
interface Explanation {
|
|
value: number;
|
|
description: string;
|
|
details: Explanation[];
|
|
}
|
|
|
|
interface SearchResponse<T> {
|
|
took: number;
|
|
timed_out: boolean;
|
|
_scroll_id?: string;
|
|
_shards: ShardsResponse;
|
|
hits: {
|
|
total: number;
|
|
max_score: number;
|
|
hits: Array<{
|
|
_index: string;
|
|
_type: string;
|
|
_id: string;
|
|
_score: number;
|
|
_source: T;
|
|
_version?: number;
|
|
_explanation?: Explanation;
|
|
fields?: any;
|
|
highlight?: any;
|
|
inner_hits?: any;
|
|
matched_queries?: string[];
|
|
sort?: string[];
|
|
}>;
|
|
};
|
|
aggregations?: any;
|
|
}
|
|
|
|
// Define the interface of the source object
|
|
interface Source {
|
|
foo: string
|
|
}
|
|
|
|
async function run () {
|
|
// All of the examples below are valid code, by default,
|
|
// the request body will be `RequestBody` and response will be `ResponseBody`.
|
|
const response = await client.search({
|
|
index: 'test',
|
|
body: {
|
|
query: {
|
|
match: { foo: 'bar' }
|
|
}
|
|
}
|
|
})
|
|
// body here is `ResponseBody`
|
|
console.log(response.body)
|
|
|
|
// The first generic is the request body
|
|
const response = await client.search<SearchBody>({
|
|
index: 'test',
|
|
// Here the body must follow the `SearchBody` interface
|
|
body: {
|
|
query: {
|
|
match: { foo: 'bar' }
|
|
}
|
|
}
|
|
})
|
|
// body here is `ResponseBody`
|
|
console.log(response.body)
|
|
|
|
const response = await client.search<SearchBody, SearchResponse<Source>>({
|
|
index: 'test',
|
|
// Here the body must follow the `SearchBody` interface
|
|
body: {
|
|
query: {
|
|
match: { foo: 'bar' }
|
|
}
|
|
}
|
|
})
|
|
// Now you can have full type definition of the response
|
|
console.log(response.body)
|
|
}
|
|
|
|
run().catch(console.log)
|
|
----
|