TypeScript: GeoShape.coordinates() missing support for Polygon geometry (number[][][])

[FBenazizMT]

Bug Description

The TypeScript definition for GeoShape.coordinates() is incomplete and doesn't support Polygon geometries.
https://docs.opensearch.org/latest/field-types/supported-field-types/geo-shape/#polygon

Current Type Definition

coordinates(coords: number[][] | number[]): this;

Issue

The current typing only supports:

Point: number[] → [longitude, latitude]

LineString: number[][] → [[lon, lat], [lon, lat], ...]

But it's missing support for:

Polygon: number[][][] → [[[lon, lat], [lon, lat], ...]]

Expected Type Definition

coordinates(coords: number[] | number[][] | number[][][]): this;

Reproduction

import builder from 'elastic-builder';

const polygonCoords: number[][] = [[2.415381, 49.383599], [2.413381, 49.38364]];

// This works at runtime but fails TypeScript compilation
const geoShape = builder
  .geoShape()
  .type('polygon')
  .coordinates([polygonCoords]); // ❌ TypeScript error

// Current workaround needed:
const geoShapeWorkaround = builder
  .geoShape()
  .type('polygon')
  .coordinates([polygonCoords] as any); // ✅ Works but requires cast

Environment

elastic-builder version: 3.2.0

TypeScript version: 5.9.2

Impact

This forces developers to use as any casts when working with Polygon geometries, losing type safety.

Thank you

[sudo-suhas]

I can't see any 3 dimensional array in the docs on this page - https://www.elastic.co/docs/reference/query-languages/query-dsl/query-dsl-geo-shape-query

Also, the example you have shared is using a 2 dimensional array which is supported by the type defined. If you are using AI to fill out the issue details, would be good to double check what it spits out before creating the issue.

[FBenazizMT]

I can't see any 3 dimensional array in the docs on this page - https://www.elastic.co/docs/reference/query-languages/query-dsl/query-dsl-geo-shape-query

Also, the example you have shared is using a 2 dimensional array which is supported by the type defined. If you are using AI to fill out the issue details, would be good to double check what it spits out before creating the issue.

I did not made a mistake in my example it was on purpose. When I search in a 2 dimensional array I have an error on the runtime. But I do not have any error with a 3 dimensional array.

If i don't make any mistake in the GeoJSON standard it's a 3 dimensional array : https://geojson.org/geojson-spec.html#id4

I already saw the page that you gave me but unfortunately they only have written a example with an 'envelope' not a 'polygon'.
The polygon type is there : https://www.elastic.co/docs/reference/elasticsearch/mapping-reference/geo-shape
I also found another example with a polygon query : https://www.elastic.co/search-labs/blog/esql-geospatial-search-part-one

I hope I did not made any mistake on my research. I'm sorry if I did. The elastic search documentation is not really clear about this.

[sudo-suhas]

I did not made a mistake in my example

Sorry, I missed the square brackets wrapping polygonCoords when it was being passed to the function.

Thanks for sharing the sources. If you can create a PR to amend the type definition, I would be happy to merge it.