doc: update roadmap

[ymc9]

Summary by CodeRabbit

• Documentation
  • Updated roadmap with completed features including Access Control and Data Validation.
  • Added new planned features: TanStack Query integration and Custom procedures.
  • Enhanced roadmap introduction with clearer priority information.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
zenstack-new-site	Ready	Preview	Comment	Oct 20, 2025 6:36pm

💡 Enable Vercel Agent with $100 free credit for automated AI reviews

[coderabbitai]

Walkthrough

Updates roadmap documentation by marking Access Control and Data Validation as completed, adding new roadmap items for TanStack Query integration and Custom procedures, including an introductory description, and removing the Json filter item.

Changes

Cohort / File(s)	Summary
Roadmap documentation update versioned_docs/version-3.x/roadmap.md	Updated roadmap items: marked Access Control and Data Validation as completed; added new items for TanStack Query integration and Custom procedures; added introductory paragraph describing roadmap and priority; removed Json filter item; retained Zod integration as pending

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The pull request title "doc: update roadmap" directly relates to the main change in the changeset, which involves updating the roadmap documentation file (versioned_docs/version-3.x/roadmap.md). The title clearly communicates that this is a documentation update focused on the roadmap, which accurately reflects the primary change. The title is concise, uses appropriate conventions (the "doc:" prefix indicates documentation), and is specific enough that a reviewer scanning the commit history would understand the nature of the change without confusion. While the title doesn't detail every modification (such as marking items as completed or adding new features), this level of specificity is appropriate and not expected in a pull request title.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch doc/update-roadmap

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

versioned_docs/version-3.x/roadmap.md (1)

12-15: New roadmap items added consistently.

The formatting is consistent with existing items. The new features (TanStack Query integration and Custom procedures) are reasonable roadmap additions. Consider adding brief one-line descriptions for context if you want to match the detail level of other major items in the future.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8000a8e and c651511.

📒 Files selected for processing (1)

• versioned_docs/version-3.x/roadmap.md (1 hunks)

🔇 Additional comments (2)

versioned_docs/version-3.x/roadmap.md (2)

7-8: Clear and helpful roadmap introduction.

The new introductory paragraph effectively explains the roadmap's purpose, manages expectations around timeline, and clarifies the priority ordering. This adds valuable context for readers.

---

9-10: Appropriate completion status updates.

Marking Access Control and Data Validation as completed reflects the current project status and is appropriately documented in the roadmap.