Skip to content

fix: correct _geoBoundingBox corner labels (top-left/bottom-right → top-right/bottom-left)#3561

Merged
qdequele merged 1 commit intomeilisearch:mainfrom
FarouHub:fix/geo-bounding-box-corners
Apr 27, 2026
Merged

fix: correct _geoBoundingBox corner labels (top-left/bottom-right → top-right/bottom-left)#3561
qdequele merged 1 commit intomeilisearch:mainfrom
FarouHub:fix/geo-bounding-box-corners

Conversation

@FarouHub
Copy link
Copy Markdown
Contributor

@FarouHub FarouHub commented Apr 20, 2026

Description

The filter_by_geo_bounding_box.mdx page incorrectly describes the two coordinate pairs of _geoBoundingBox as top-left / bottom-right. According to the official specification, the correct corners are top-right / bottom-left.

AI used to write issue and PR descriptions.

Fixes #3560

Changes

  • Replaced all references to "top-left" / "bottom-right" with "top-right" / "bottom-left"
  • Updated parameter names: topLeftLat/topLeftLng/bottomRightLat/bottomRightLng → topRightLat/topRightLng/bottomLeftLat/bottomLeftLng
  • Fixed the JavaScript map example to use [ne.lat, ne.lng] and [sw.lat, sw.lng] instead of mixing NE/SW coordinates

Checklist

For external maintainers

  • Did you use any AI tool while implementing this PR (code, tests, docs, etc.)? If yes, disclose it in the PR description and describe what it was used for. AI usage is allowed when it is disclosed.
  • Have you made sure that the title is accurate and descriptive of the changes?

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 20, 2026

📝 Walkthrough

Walkthrough

A documentation update to the _geoBoundingBox filter redefines the bounding rectangle coordinate order from top-left (NW) and bottom-right (SE) corners to top-right (NE) and bottom-left (SW) corners, with corresponding updates to parameter descriptions and code examples.

Changes

Cohort / File(s) Summary
Geo Bounding Box Documentation
capabilities/geo_search/how_to/filter_by_geo_bounding_box.mdx
Updated coordinate pair ordering from (NW, SE) to (NE, SW) corners, revised parameter descriptions and inequality conditions, and modified example code to reflect new coordinate semantics.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Poem

🐰 Our bounding box has pirouetted round,
Northeast meets southwest, new corners found,
Coordinates waltz to a different beat,
Documentation now clean and neat! ✨
Geo-search clarity takes the stage,
A better corner dance on the page! 📍

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title directly and clearly describes the main change: correcting the corner labels in the _geoBoundingBox documentation from top-left/bottom-right to top-right/bottom-left, which matches the core content of the PR.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@qdequele qdequele self-requested a review April 27, 2026 14:06
Copy link
Copy Markdown
Member

@qdequele qdequele left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch! Thanks for the contribution :D

@qdequele qdequele added this pull request to the merge queue Apr 27, 2026
Merged via the queue into meilisearch:main with commit 0218eb2 Apr 27, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

_geoBoundingBox documentation incorrectly describes corners as top-left / bottom-right instead of top-right / bottom-left

2 participants