Skip to content

Conversation

@ymc9
Copy link
Member

@ymc9 ymc9 commented Aug 30, 2025

Summary by CodeRabbit

  • Documentation
    • Feature list updated; several items now marked “coming soon” (e.g., built-in access control, automatic CRUD APIs, TanStack Query hooks).
    • “Get started” renamed to “Quick start.”
    • Extensive in-repo documentation removed and consolidated.
    • Added prominent links directing readers to the external documentation site: https://zenstack.dev/docs/3.x/ (including migration guidance).

Copilot AI review requested due to automatic review settings August 30, 2025 02:57
@coderabbitai
Copy link

coderabbitai bot commented Aug 30, 2025

Caution

Review failed

The pull request is closed.

Walkthrough

README.md was streamlined: three feature bullets were annotated “(coming soon)”, the “Get started” heading was renamed “Quick start”, extensive in-repo documentation sections were removed, and remaining guidance now points to external docs at https://zenstack.dev/docs/3.x/ (including the database-migration anchor).

Changes

Cohort / File(s) Summary of Changes
Docs overhaul
README.md
Marked multiple feature bullets as “(coming soon)”; renamed “Get started” to “Quick start”; removed extensive in-repo documentation sections and examples; added links directing readers to external documentation at https://zenstack.dev/docs/3.x/ (including .../orm/migration).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

Poem

I’m a rabbit with a README in my paw,
I hopped the docs to an external maw.
“Coming soon” I whisper, quick start in sight,
Tucked long pages away, left a tidy light.
Thump and bound — link given, off to the night. 🐇📚


📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 3b3dfab and 6c53a4e.

📒 Files selected for processing (1)
  • README.md (3 hunks)
✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch chore/readme-2

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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbitai ignore or @coderabbit ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR updates the README.md file to simplify the documentation and reflect the current state of ZenStack v3 features. The main purpose is to streamline the README by removing extensive implementation details and directing users to the dedicated documentation site.

  • Marks several features as "coming soon" to accurately reflect their development status
  • Changes "Get started" section title to "Quick start" for better clarity
  • Replaces detailed implementation documentation with a link to the official documentation site

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

@claude
Copy link

claude bot commented Aug 30, 2025

Claude finished @ymc9's task —— View job


README Update Review

I've completed my review of this README simplification PR. Here's my comprehensive feedback:

Todo List:

  • Read the current README.md file
  • Analyze the git diff to understand exact changes
  • Review documentation quality and accuracy
  • Check for potential issues or improvements
  • Provide comprehensive feedback

Summary of Changes

This PR significantly simplifies the README by removing 331 lines of detailed implementation documentation and making these key changes:

  1. Feature status updates: Added "(coming soon)" to 3 features that aren't yet available
  2. Section rename: "Get started" → "Quick start"
  3. Content removal: Eliminated extensive sections on implementation details, API usage, plugins, and limitations
  4. Documentation redirect: Replaced detailed content with a simple link to the doc site

Review Feedback

Positive Changes

  1. Accurate feature status: The "(coming soon)" additions correctly reflect the current development state:

    • Built-in access control and data validation
    • Automatic CRUD web APIs with adapters
    • TanStack Query hooks integration
  2. Improved clarity: "Quick start" is more descriptive than "Get started"

  3. Reduced maintenance burden: Moving detailed docs to the dedicated site prevents README/documentation drift

⚠️ Potential Concerns

  1. Missing context for removed limitations section: The limitations section (lines 358-364 in old README) contained important information about current constraints:

    • Only SQLite and Postgres support
    • No Prisma client extensions support
    • No JSON field filtering support
    • No raw SQL query APIs

    Recommendation: Consider adding a brief "Current Limitations" section or ensure this critical information is prominently displayed on the doc site.

  2. Loss of quick reference: Users now need to visit external docs for basic usage patterns. The removed sections provided valuable quick-reference material for:

    • Database connection setup
    • Basic CRUD examples
    • Plugin usage patterns
  3. Broken internal reference: Line 50 still references "See database migration" but this section was removed.

    Fix needed: Either remove this reference or update it to point to the doc site.

🔧 Suggested Improvements

  1. Fix broken reference: Update line 50 to either remove the reference or link to doc site migration section

  2. Consider keeping a minimal "Limitations" section: Since ZenStack v3 is in alpha, users should be aware of current limitations before trying it

  3. Add migration guide reference: The removed migration section was valuable - consider adding a link to doc site migration guide

📋 Code Quality Assessment

  • Documentation Quality: ✅ Good - Clear, concise, well-structured
  • Accuracy: ⚠️ Minor issue - One broken internal reference
  • Completeness: ⚠️ Consider - Some important context was removed
  • Maintainability: ✅ Excellent - Much easier to maintain

🔒 Security & Performance

  • No security or performance implications for README changes
  • All external links use HTTPS appropriately

🧪 Test Coverage

  • Not applicable for documentation changes
  • Consider adding doc site link validation if not already present

Final Recommendation

This is a good simplification that aligns with best practices for project READMEs. The main issues are:

  1. Must fix: Broken internal reference on line 50
  2. Should consider: Adding back a brief limitations section given alpha status

The overall direction is sound - directing users to comprehensive documentation while keeping the README focused on core value proposition and getting started.


Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Nitpick comments (6)
README.md (6)

32-36: “Coming soon” bullets: consider adding status links or timeline

Good to set expectations. Optionally add links to tracking issues/roadmap for these three bullets to improve clarity.

Confirm these features are indeed not available in the current alpha builds.


52-52: Preserve legacy anchor for “Get started”

External references might still point to #get-started. Add a hidden anchor to avoid link rot.

+<a id="get-started"></a>
 # Quick start

85-87: Docs pointer is clear; consider adding 3–5 deep links

Add direct links (e.g., “Install,” “Generate schema,” “Database migration,” “Kysely query builder,” “Policies”) to reduce bounce and help SEO.

I can propose specific deep links if you share the preferred doc slugs.


34-34: Hyphenation nit: “life-cycle” → “lifecycle”

Minor consistency/grammar polish.

- - Designed for extensibility and flexibility: plugins, life-cycle hooks, etc.
+ - Designed for extensibility and flexibility: plugins, lifecycle hooks, etc.

3-6: Add alt text for logo for accessibility

Include alt text on the img within the picture element.

-    <img src="https://raw.githubusercontent.com/zenstackhq/zenstack-docs/main/static/img/logo.png" height="128">
+    <img alt="ZenStack logo" src="https://raw.githubusercontent.com/zenstackhq/zenstack-docs/main/static/img/logo.png" height="128">

19-21: License badge points to different repo

Link targets the main repo’s LICENSE. Verify this is intentional for V3; otherwise point to this repo’s LICENSE.

I can update the link once you confirm the desired target.

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 35f875b and 3b3dfab.

📒 Files selected for processing (1)
  • README.md (3 hunks)
🧰 Additional context used
🧠 Learnings (4)
📚 Learning: 2025-08-04T08:43:33.161Z
Learnt from: CR
PR: zenstackhq/zenstack-v3#0
File: CLAUDE.md:0-0
Timestamp: 2025-08-04T08:43:33.161Z
Learning: Kysely-Based ORM: V3 uses Kysely as query builder instead of Prisma runtime dependency

Applied to files:

  • README.md
📚 Learning: 2025-08-04T08:43:33.161Z
Learnt from: CR
PR: zenstackhq/zenstack-v3#0
File: CLAUDE.md:0-0
Timestamp: 2025-08-04T08:43:33.161Z
Learning: No runtime dependency on prisma/client

Applied to files:

  • README.md
📚 Learning: 2025-08-04T08:43:33.161Z
Learnt from: CR
PR: zenstackhq/zenstack-v3#0
File: CLAUDE.md:0-0
Timestamp: 2025-08-04T08:43:33.161Z
Learning: `zenstack generate` compiles ZModel to TypeScript schema (`schema.ts`)

Applied to files:

  • README.md
📚 Learning: 2025-08-04T08:43:33.161Z
Learnt from: CR
PR: zenstackhq/zenstack-v3#0
File: CLAUDE.md:0-0
Timestamp: 2025-08-04T08:43:33.161Z
Learning: Schema-first approach with ZModel DSL extension of Prisma schema language

Applied to files:

  • README.md
🪛 LanguageTool
README.md

[grammar] ~34-~34: There might be a mistake here.
Context: ...ibility: plugins, life-cycle hooks, etc. - Automatic CRUD web APIs with adapters fo...

(QB_NEW_EN)


[grammar] ~35-~35: There might be a mistake here.
Context: ...ers for popular frameworks (coming soon) - Automatic [TanStack Query](https://githu...

(QB_NEW_EN)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: build-test (20.x)

@claude
Copy link

claude bot commented Aug 30, 2025

Claude finished @ymc9's task —— View job


README Update Review

I've completed my review of this README simplification PR. Here's my comprehensive feedback:

Todo List:

  • Read the current README.md file
  • Analyze the git diff to understand exact changes
  • Review documentation quality and accuracy
  • Check for potential issues or improvements
  • Provide comprehensive feedback

Summary of Changes

This PR significantly simplifies the README by removing 331 lines of detailed implementation documentation and making these key changes:

  1. Feature status updates: Added "(coming soon)" to 3 features that aren't yet available
  2. Section rename: "Get started" → "Quick start"
  3. Content removal: Eliminated extensive sections on implementation details, API usage, plugins, and limitations
  4. Documentation redirect: Replaced detailed content with a simple link to the doc site

Review Feedback

Positive Changes

  1. Accurate feature status: The "(coming soon)" additions correctly reflect the current development state:

    • Built-in access control and data validation
    • Automatic CRUD web APIs with adapters
    • TanStack Query hooks integration
  2. Improved clarity: "Quick start" is more descriptive than "Get started"

  3. Reduced maintenance burden: Moving detailed docs to the dedicated site prevents README/documentation drift

⚠️ Potential Concerns

  1. Missing context for removed limitations section: The limitations section (lines 358-364 in old README) contained important information about current constraints:

    • Only SQLite and Postgres support
    • No Prisma client extensions support
    • No JSON field filtering support
    • No raw SQL query APIs

    Recommendation: Consider adding a brief "Current Limitations" section or ensure this critical information is prominently displayed on the doc site.

  2. Loss of quick reference: Users now need to visit external docs for basic usage patterns. The removed sections provided valuable quick-reference material for:

    • Database connection setup
    • Basic CRUD examples
    • Plugin usage patterns
  3. Broken internal reference: Line 50 still references "See database migration" but this section was removed.

    Fix needed: Either remove this reference or update it to point to the doc site.

🔧 Suggested Improvements

  1. Fix broken reference: Update line 50 to either remove the reference or link to doc site migration section

  2. Consider keeping a minimal "Limitations" section: Since ZenStack v3 is in alpha, users should be aware of current limitations before trying it

  3. Add migration guide reference: The removed migration section was valuable - consider adding a link to doc site migration guide

📋 Code Quality Assessment

  • Documentation Quality: ✅ Good - Clear, concise, well-structured
  • Accuracy: ⚠️ Minor issue - One broken internal reference
  • Completeness: ⚠️ Consider - Some important context was removed
  • Maintainability: ✅ Excellent - Much easier to maintain

🔒 Security & Performance

  • No security or performance implications for README changes
  • All external links use HTTPS appropriately

🧪 Test Coverage

  • Not applicable for documentation changes
  • Consider adding doc site link validation if not already present

Final Recommendation

This is a good simplification that aligns with best practices for project READMEs. The main issues are:

  1. Must fix: Broken internal reference on line 50
  2. Should consider: Adding back a brief limitations section given alpha status

The overall direction is sound - directing users to comprehensive documentation while keeping the README focused on core value proposition and getting started.


@ymc9 ymc9 merged commit 31873bf into dev Aug 30, 2025
3 of 4 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.

2 participants