Spatial columns announcement #2420
Conversation
WalkthroughAdds a new blog post page at src/routes/blog/post/announcing-spatial-columns/+page.markdoc introducing Spatial columns with point/line/polygon types, a spatial index, and 12 geo operators, plus availability notes and links. Adds a changelog entry at src/routes/changelog/(entries)/2025-09-18.markdoc announcing the Spatial Columns API with use cases and an external announcement link. Includes a new image asset under static/images/blog/announcing-spatial-columns/images. No changes to exported or public entities. Suggested reviewers
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches🧪 Generate unit tests
Tip 👮 Agentic pre-merge checks are now available in preview!Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.
Please see the documentation for more information. Example: reviews:
pre_merge_checks:
custom_checks:
- name: "Undocumented Breaking Changes"
mode: "warning"
instructions: |
Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).Please share your feedback with us on this Discord post. 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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
static/images/blog/announcing-spatial-columns/images (1)
1-2: Remove stray file and add missing cover imageBoth the post and changelog reference /images/blog/announcing-spatial-columns/cover.png but static/ lacks that file; remove the stray file and add the actual cover.
- References to fix: src/routes/blog/post/announcing-spatial-columns/+page.markdoc (cover) and src/routes/changelog/(entries)/2025-09-18.markdoc (cover).
- Remove: static/images/blog/announcing-spatial-columns/images
- Add: static/images/blog/announcing-spatial-columns/cover.png
- static/images/blog/announcing-spatial-columns/images + static/images/blog/announcing-spatial-columns/cover.png
🧹 Nitpick comments (5)
src/routes/changelog/(entries)/2025-09-18.markdoc (1)
7-11: Tighten opening copy (optional).“Announcing: API for spatial columns” immediately repeats the front‑matter title. Consider removing this line to avoid redundancy.
-Announcing: API for spatial columns +src/routes/blog/post/announcing-spatial-columns/+page.markdoc (4)
16-16: Product naming consistency.Use “Appwrite Databases” (product name) instead of “Appwrite Database”.
-That’s why we’re introducing **Spatial columns and queries**. Now, you can store points, lines, and polygons directly in Appwrite Database, index them efficiently, and query how they interact with each other. No hacks or workarounds required. +That’s why we’re introducing **Spatial columns and queries**. Now, you can store points, lines, and polygons directly in Appwrite Databases, index them efficiently, and query how they interact with each other. No hacks or workarounds required.
33-44: List renders as a code block due to indentation.The 12 operators are indented by 4 spaces, which Markdoc/Markdown will treat as a code block. Outdent to regular bullets.
- - `crosses` - - `notCrosses` - - `distanceEqual` - - `distanceNotEqual` - - `distanceGreaterThan` - - `distanceLessThan` - - `intersects` - - `notIntersects` - - `overlaps` - - `notOverlaps` - - `touches` - - `notTouches` +- `crosses` +- `notCrosses` +- `distanceEqual` +- `distanceNotEqual` +- `distanceGreaterThan` +- `distanceLessThan` +- `intersects` +- `notIntersects` +- `overlaps` +- `notOverlaps` +- `touches` +- `notTouches`
25-28: Minor tone/typography cleanup.Avoid the arrow “→” in prose bullets to keep style consistent with the rest of the docs.
-- `polygon`: → Great for delivery zones, property boundaries, or compliance regions. +- `polygon`: Great for delivery zones, property boundaries, or compliance regions.
73-76: Unify bullet style.Same arrow glyph here; use plain text for consistency.
- - `point` → single locations (shops, vehicles, users) - - `line` → paths and routes - - `polygon` → service areas, regions, or geofences + - `point`: single locations (shops, vehicles, users) + - `line`: paths and routes + - `polygon`: service areas, regions, or geofences
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
static/images/blog/announcing-spatial-columns/cover.pngis excluded by!**/*.png
📒 Files selected for processing (3)
src/routes/blog/post/announcing-spatial-columns/+page.markdoc(1 hunks)src/routes/changelog/(entries)/2025-09-18.markdoc(1 hunks)static/images/blog/announcing-spatial-columns/images(1 hunks)
🔇 Additional comments (3)
src/routes/changelog/(entries)/2025-09-18.markdoc (1)
3-7: Front matter looks correct; ensure cover path resolves.Title/date/layout are fine. Just make sure
/images/blog/announcing-spatial-columns/cover.pngexists (see image comment). Otherwise the entry will show a broken cover.Use the image verification script in the image comment to confirm the asset is present.
src/routes/blog/post/announcing-spatial-columns/+page.markdoc (2)
86-90: Verify internal links resolve.
- Blog post slugs exist in-repo: src/routes/blog/post/announcing-inversion-queries/+page.markdoc and src/routes/blog/post/announcing-appwrite-databases-new-ui/+page.markdoc.
- /docs/products/databases/geo-queries not found in this repository — confirm that docs page is published (or update the link) to avoid a 404.
8-10: Author/category validated in frontmatter — confirm central author registry.
author: jake-barnby appears across multiple posts; category: announcement is used elsewhere. Scan did not find a central authors slug list—confirm 'jake-barnby' is defined in your authors data or CMS. File: src/routes/blog/post/announcing-spatial-columns/+page.markdoc (lines 8–10).
| layout: post | ||
| title: "Announcing API for spatial columns: Build scalable location-aware apps with ease" | ||
| description: Handle maps, geofencing, routing, and compliance zones natively in Appwrite | ||
| date: 2025-98-18 |
There was a problem hiding this comment.
Invalid date format breaks sorting/build.
2025-98-18 has an impossible month. Use 2025-09-18.
-date: 2025-98-18
+date: 2025-09-18📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| date: 2025-98-18 | |
| date: 2025-09-18 |
🤖 Prompt for AI Agents
In src/routes/blog/post/announcing-spatial-columns/+page.markdoc around line 5,
the frontmatter date is invalid ("2025-98-18" has month 98) which breaks
sorting/build; update the date to a valid YYYY-MM-DD value (replace "2025-98-18"
with "2025-09-18") and ensure the frontmatter date uses the standard ISO format.
| title: "Announcing API for spatial columns: Build scalable location-aware apps with ease" | ||
| description: Handle maps, geofencing, routing, and compliance zones natively in Appwrite | ||
| date: 2025-98-18 | ||
| cover: /images/blog/announcing-spatial-columns/cover.png |
There was a problem hiding this comment.
Cover path likely missing.
cover: /images/blog/announcing-spatial-columns/cover.png is referenced, but no such file was added. See image comment to add the asset or update the path.
🤖 Prompt for AI Agents
In src/routes/blog/post/announcing-spatial-columns/+page.markdoc around line 6,
the frontmatter references cover:
/images/blog/announcing-spatial-columns/cover.png but that file was not added;
either add the image asset at that exact path in the repository (e.g., place the
file at static/images/blog/announcing-spatial-columns/cover.png or your repo's
public/static image folder so the URL resolves) or update the cover value to
point to an existing image path; commit the added image or update the path in
the markdoc file accordingly.
1 participant
What does this PR do?
(Provide a description of what this PR does.)
Test Plan
(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work.)
Related PRs and Issues
(If this PR is related to any other PR or resolves any issue or related to any issue link all related PR and issues here.)
Have you read the Contributing Guidelines on issues?
(Write your answer here.)
Summary by CodeRabbit