Skip to content

feat: make geohashPrecision optional in search#14

Open
johnf wants to merge 1 commit intomainfrom
feat/geohash-precision-optional
Open

feat: make geohashPrecision optional in search#14
johnf wants to merge 1 commit intomainfrom
feat/geohash-precision-optional

Conversation

@johnf
Copy link
Copy Markdown
Collaborator

@johnf johnf commented Mar 27, 2026

Summary

  • Allow search requests to omit geohashPrecision instead of requiring it with a default
  • Geohash aggregation is only built when both precision and bounding box are provided

Test plan

  • pnpm lint passes
  • pnpm test passes
  • Search requests without geohashPrecision no longer fail validation

@github-actions
Copy link
Copy Markdown

github-actions bot commented Mar 27, 2026

Coverage Report

Status Category Percentage Covered / Total
🔵 Lines 100% (🎯 100%) 329 / 329
🔵 Statements 100% (🎯 100%) 339 / 339
🔵 Functions 100% (🎯 100%) 51 / 51
🔵 Branches 100% (🎯 100%) 159 / 159
File Coverage
File Stmts Branches Functions Lines Uncovered Lines
Changed Files
src/routes/search.ts 100% 100% 100% 100%
src/utils/queryBuilder.ts 100% 100% 100% 100%
Generated in workflow #53 for commit 239af2c by the Vitest Coverage Report Action

Allow search requests to omit geohashPrecision instead of requiring it
with a default. Geohash aggregation is only built when both precision
and bounding box are provided.
@johnf johnf force-pushed the feat/geohash-precision-optional branch from 6dee2ca to 239af2c Compare March 27, 2026 05:13
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.

2 participants