Release v0.3 compatibility and query upgrades - #2
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
queryLocationswith fuzzy search, bounding boxes, proximity/radius filtering, and pagination.v0.3.0.v0.2.0changelog date.Why
This addresses the remaining developer-facing limitations identified after
v0.2.0, while leaving coordinate completeness, coordinate confidence, and Dhivehi names for later work.Developer impact
Existing ESM imports remain compatible. CommonJS consumers can now use
require(), and applications can perform typo-tolerant and spatial queries without adding another library.Validation
npm run typechecknpm run check:generatednpm test— 13/13 tests passednpm pack --dry-run --json— package manifest verified