chore: bump version

[ymc9]

Summary by CodeRabbit

• Documentation
  • Added a link to the NestJS Backend API tutorial in the Examples section.
  • Removed the Polymorphic Relations link.
  • Updated the status of Strong-typed JSON field to "coming soon."
• Chores
  • Updated the JetBrains IDE plugin version to 2.0.1.

[coderabbitai]

Walkthrough

Walkthrough

The recent updates include modifications to the README.md, enhancing the Examples section and updating feature statuses, alongside a minor version bump in the JetBrains IDE plugin's build.gradle.kts file. These changes aim to improve documentation clarity and ensure the software components are up-to-date.

Changes

File Path	Changes Summary
README.md	Added NestJS Backend API tutorial, removed Polymorphic Relations link, updated status of Strong-typed JSON field.
packages/ide/jetbrains/.../build.gradle.kts	Updated version from 2.0.0 to 2.0.1.

---

Recent Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 1be5d52 and 9c21aff.

Files ignored due to path filters (13)

• package.json is excluded by !**/*.json
• packages/ide/jetbrains/package.json is excluded by !**/*.json
• packages/language/package.json is excluded by !**/*.json
• packages/misc/redwood/package.json is excluded by !**/*.json
• packages/plugins/openapi/package.json is excluded by !**/*.json
• packages/plugins/swr/package.json is excluded by !**/*.json
• packages/plugins/tanstack-query/package.json is excluded by !**/*.json
• packages/plugins/trpc/package.json is excluded by !**/*.json
• packages/runtime/package.json is excluded by !**/*.json
• packages/schema/package.json is excluded by !**/*.json
• packages/sdk/package.json is excluded by !**/*.json
• packages/server/package.json is excluded by !**/*.json
• packages/testtools/package.json is excluded by !**/*.json

Files selected for processing (2)

• README.md (2 hunks)
• packages/ide/jetbrains/build.gradle.kts (1 hunks)

Additional Context Used

LanguageTool (54)

README.md (54)

Near line 28: Possible spelling mistake found.
Context: ...green"> ## What it is ZenStack is a Node.js/TypeScript toolkit that si...

---

Near line 29: Possible spelling mistake found.
Context: ...f a web app's backend. It supercharges Prisma ORM with a powerful...

---

Near line 37: Possible spelling mistake found.
Context: ...stions. ZenStack incrementally extends Prisma's power with the following four layers:...

---

Near line 39: Possible spelling mistake found.
Context: ...with the following four layers: ### 1. ZModel - an extended Prisma schema language Z...

---

Near line 39: Possible spelling mistake found.
Context: ...ur layers: ### 1. ZModel - an extended Prisma schema language ZenStack introduces a ...

---

Near line 40: Possible spelling mistake found.
Context: ...l - an extended Prisma schema language ZenStack introduces a data modeling language cal...

---

Near line 41: Possible spelling mistake found.
Context: ...oduces a data modeling language called "ZModel" - a superset of Prisma schema language...

---

Near line 41: Possible spelling mistake found.
Context: ...anguage called "ZModel" - a superset of Prisma schema language. It extended Prisma sch...

---

Near line 41: Possible spelling mistake found.
Context: ... of Prisma schema language. It extended Prisma schema with custom attributes and funct...

---

Near line 41: Possible spelling mistake found.
Context: ... a flexible access control layer around Prisma. ```ts // base.zmodel abstract model B...

---

Near line 67: Possible spelling mistake found.
Context: ...auth() != null && published) } ``` The zenstack CLI transpiles the ZModel into a stand...

---

Near line 67: Possible spelling mistake found.
Context: ...&& published) } ``` The zenstack CLI transpiles the ZModel into a standard Prisma schem...

---

Near line 67: Possible spelling mistake found.
Context: ... ``` The zenstack CLI transpiles the ZModel into a standard Prisma schema, which yo...

---

Near line 67: Possible spelling mistake found.
Context: ...I transpiles the ZModel into a standard Prisma schema, which you can use with the regu...

---

Near line 67: Possible spelling mistake found.
Context: ...ema, which you can use with the regular Prisma workflows. ### 2. Runtime enhancements...

---

Near line 69: Possible spelling mistake found.
Context: ...kflows. ### 2. Runtime enhancements to Prisma client At runtime, transparent proxies...

---

Near line 71: Possible spelling mistake found.
Context: ... transparent proxies are created around Prisma clients for intercepting queries and mu...

---

Near line 90: Possible spelling mistake found.
Context: ...help you wrap an access-control-enabled Prisma client into backend CRUD APIs that can ...

---

Near line 137: Possible spelling mistake found.
Context: ...s a high-level architecture overview of ZenStack. ![Architecture](https://zenstack.dev/...

---

Near line 151: Possible spelling mistake found.
Context: ...data validation rules right inside your Prisma schema - Auto-generated OpenAPI (REST...

---

Near line 152: Possible spelling mistake found.
Context: ...e your Prisma schema - Auto-generated OpenAPI (RESTful) specifications, services, and...

---

Near line 160: Possible spelling mistake found.
Context: ...mpromised performance ### Plugins - Prisma schema generator - Zod schema generat...

---

Near line 161: Possible spelling mistake found.
Context: ...lugins - Prisma schema generator - Zod schema generator - [SWR](https://gith...

---

Near line 162: Unpaired symbol: ‘[’ seems to be missing
Context: ...erator - Zod schema generator - SWR and [Tan...

---

Near line 162: Possible spelling mistake found.
Context: ...WR](https://github.com/vercel/swr) and [TanStack Query](https://github.com/TanStack/quer...

---

Near line 163: Possible spelling mistake found.
Context: ...com/TanStack/query) hooks generator - OpenAPI specification generator - [tRPC](http...

---

Near line 164: Possible spelling mistake found.
Context: ... OpenAPI specification generator - tRPC router generator - ...

---

Near line 164: Unpaired symbol: ‘[’ seems to be missing
Context: ...penAPI specification generator - tRPC router generator - ?...

---

Near line 170: Possible spelling mistake found.
Context: ...new "app directory" in Next.js 13) - [Nuxt](https://zenstack.dev/docs/reference/se...

---

Near line 172: Possible spelling mistake found.
Context: ...ference/server-adapters/sveltekit) - [Fastify](https://zenstack.dev/docs/reference/se...

---

Near line 173: The official spelling of this programming framework is “Express.js”.
Context: ...reference/server-adapters/fastify) - [ExpressJS](https://zenstack.dev/docs/reference/se...

---

Near line 174: Unpaired symbol: ‘]’ seems to be missing
Context: ...rence/server-adapters/express) - 🙋🏻 [Request for an adapter](https://discord....

---

Near line 176: Possible spelling mistake found.
Context: ...er](https://discord.gg/Ykhr738dUe) ### Prisma schema extensions - [Custom attribut...

---

Near line 182: Unpaired symbol: ‘]’ seems to be missing
Context: ...typed JSON field (coming soon) - 🙋🏻 [Request for an extension](https://discor...

---

Near line 191: Possible spelling mistake found.
Context: ...es the following patterns: - ACL - RBAC - ABAC - Multi-Tenancy You can use...

---

Near line 192: Possible spelling mistake found.
Context: ...llowing patterns: - ACL - RBAC - ABAC - Multi-Tenancy You can use [this bl...

---

Near line 197: It appears that a hyphen is missing in the noun “To-do” (= task) or did you mean the verb “to do”?
Context: ...) as an introduction. ### Multi-Tenant Todo App Check out the [Multi-tenant Todo A...

---

Near line 199: It appears that a hyphen is missing in the noun “To-do” (= task) or did you mean the verb “to do”?
Context: ...t Todo App Check out the Multi-tenant Todo App...

---

Near line 201: Possible spelling mistake found.
Context: ...plementations below: - [Next.js 13 + NextAuth + SWR](https://github.com/zenstackhq/sa...

---

Near line 202: Possible spelling mistake found.
Context: ...q/sample-todo-nextjs) - [Next.js 13 + NextAuth + TanStack Query](https://github.com/ze...

---

Near line 202: Possible spelling mistake found.
Context: ...do-nextjs) - [Next.js 13 + NextAuth + TanStack Query](https://github.com/zenstackhq/sa...

---

Near line 203: Possible spelling mistake found.
Context: ...todo-nextjs-tanstack) - [Next.js 13 + NextAuth + tRPC](https://github.com/zenstackhq/s...

---

Near line 203: Possible spelling mistake found.
Context: ...-tanstack) - [Next.js 13 + NextAuth + tRPC](https://github.com/zenstackhq/sample-t...

---

Near line 204: Possible spelling mistake found.
Context: ...b.com/zenstackhq/sample-todo-trpc) - [Nuxt V3 + TanStack Query](https://github.com...

---

Near line 204: Possible spelling mistake found.
Context: ...tackhq/sample-todo-trpc) - [Nuxt V3 + TanStack Query](https://github.com/zenstackhq/sa...

---

Near line 205: Possible spelling mistake found.
Context: ...ckhq/sample-todo-nuxt) - [SvelteKit + TanStack Query](https://github.com/zenstackhq/sa...

---

Near line 206: Possible spelling mistake found.
Context: .../zenstackhq/sample-todo-sveltekit) - [RedwoodJS](https://github.com/zenstackhq/sample-t...

---

Near line 211: Possible spelling mistake found.
Context: ...l-nextjs) - [Next.js 13 + App Route + ReactQuery](https://github.com/zenstackhq/docs-tut...

---

Near line 212: Possible spelling mistake found.
Context: ...-app-dir) - [Next.js 13 + App Route + tRPC](https://github.com/zenstackhq/sample-b...

---

Near line 213: Possible spelling mistake found.
Context: ...ackhq/sample-blog-nextjs-app-trpc) - [Nuxt V3 + TanStack Query](https://github.com...

---

Near line 213: Possible spelling mistake found.
Context: ...le-blog-nextjs-app-trpc) - [Nuxt V3 + TanStack Query](https://github.com/zenstackhq/do...

---

Near line 216: Possible spelling mistake found.
Context: ...om/zenstackhq/docs-tutorial-remix) - [NestJS Backend API](https://github.com/zenstac...

---

Near line 228: Consider using a different verb to strengthen your wording.
Context: ...ps://github.com/sponsors/zenstackhq) to speed up the development. Your contribution will...

---

Near line 246: Possible spelling mistake found.
Context: ...l the contributors who have helped make ZenStack better! #### Source <a href="https://...

Additional comments not posted (3)

packages/ide/jetbrains/build.gradle.kts (1)

12-12: Version updated from "2.0.0" to "2.0.1" to reflect minor improvements or bug fixes.

README.md (2)

180-180: Removed link to "Polymorphic Relations" which might be outdated or irrelevant now.

---

216-216: Added a tutorial link for "NestJS Backend API" in the Examples section.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

Note: Auto-reply has been disabled for this repository by the repository owner. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

• 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. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• 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.