Dominik Schmidt e43fe13066 fix(kql): normalise geo.bbox latitude order for backend-consistent behaviour ...

Sorts the two latitudes in the KQL layer so MinLat <= MaxLat. Only bleve
strictly requires it (it errors on an inverted box; OpenSearch tolerates it),
but doing it centrally keeps behaviour consistent across backends and the AST
easy to reason about. Longitude order is preserved so an antimeridian-crossing
box (minLon > maxLon) still works, which both backends handle identically.

2026-09-03 01:58:11 +02:00

..

test

fix(search): answer the same on both engines

2026-08-31 10:44:03 +02:00

ast.go

fix(kql): normalise geo.bbox latitude order for backend-consistent behaviour

2026-09-03 01:58:11 +02:00